Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command line parameter suggestion to run a stable archival node #72

Closed
breezytm opened this issue May 12, 2023 · 8 comments
Closed

Command line parameter suggestion to run a stable archival node #72

breezytm opened this issue May 12, 2023 · 8 comments
Assignees

Comments

@breezytm
Copy link

breezytm commented May 12, 2023

Hi, Just curious to see if anyone would be willing to share their command line if they are running a stable archival node. My node is constantly trailing behind and I find myself frequently rebooting it to stay synced.

My current setup
Docker image ghcr.io/node-real/bsc-erigon:1.0.3

command:
      - --chain=bsc
      - --datadir=/root/.local/share/erigon
      - --port=30303
      - --private.api.addr=0.0.0.0:9090
      - --torrent.port=42069
      - --torrent.download.rate=1000mb
      - --torrent.download.slots=6
      - --p2p.protocol=66
      - --downloader.verify
      - --batchSize=512M
      - --etl.bufferSize=512M
      - --db.pagesize=16k
      - --healthcheck
      - --log.console.verbosity=info
   
@harveyff
Copy link

hi, maybe i can give you some useful advice,

It has little to do with the startup command. Your startup command seems to be fine. It may be related to the following two factors.

  1. How about the hardware of the machine? Is nvme used or is there enough memory, in my case I use im4gn.4xlarge instance from aws.

  2. Are the data sources up to date? It is recommended to find a new machine (meet the above conditions), re-download the data source from https://github.com/bnb-chain/bsc-snapshots, and then start your program (it does not take much time, unzip from the download I It took a total of 20 hours).

In my case, it used to always be behind blocks because my data source was from https://github.com/ledgerwatch/erigon/ . Later, I followed the advice, re-downloaded the snapshot data and restarted synchronizing. It has been more than a week now, and I have never been behind by more than 3 minutes (I have a monitor, and when it is more than 3 minutes behind, it will send an alarm)

@icculp
Copy link

icculp commented May 16, 2023

image

@blxdyx
Copy link
Collaborator

blxdyx commented May 16, 2023

It seem work stable for our mainnet archive node.

--p2p.protocol=66 
--metrics.addr=0.0.0.0 
--db.pagesize=16k 
--datadir ./data 
--private.api.addr=localhost:9090 
--chain=bsc 
--metrics 

For bsc testnet, suggest to specify static node, add this: bootnodes=enode://0637d1e62026e0c8685b1db0ca1c767c78c95c3fab64abc468d1a64b12ca4b530b46b8f80c915aec96f74f7ffc5999e8ad6d1484476f420f0c10e3d42361914b@52.199.214.252:30311,enode://330d768f6de90e7825f0ea6fe59611ce9d50712e73547306846a9304663f9912bf1611037f7f90f21606242ded7fb476c7285cb7cd792836b8c0c5ef0365855c@18.181.52.189:30311,enode://df1e8eb59e42cad3c4551b2a53e31a7e55a2fdde1287babd1e94b0836550b489ba16c40932e4dacb16cba346bd442c432265a299c4aca63ee7bb0f832b9f45eb@52.51.80.128:30311,enode://0bd566a7fd136ecd19414a601bfdc530d5de161e3014033951dd603e72b1a8959eb5b70b06c87a5a75cbf45e4055c387d2a842bd6b1bd8b5041b3a61bab615cf@34.242.33.165:30311,enode://ecd664250ca19b1074dcfbfb48576a487cc18d052064222a363adacd2650f8e08fb3db9de7a7aecb48afa410eaeb3285e92e516ead01fb62598553aed91ee15e@3.209.122.123:30311,enode://665cf77ca26a8421cfe61a52ac312958308d4912e78ce8e0f61d6902e4494d4cc38f9b0dd1b23a427a7a5734e27e5d9729231426b06bb9c73b56a142f83f6b68@52.72.123.113:30311

@breezytm
Copy link
Author

I am in the process of redeploying my instances but two people confirmed removing --batchSize, --etl.bufferSize and --bodies.cache have stabilized their environment for mainnet. @icculp try and confirm.

@icculp
Copy link

icculp commented May 16, 2023

On v1.0.5 it's still acting up using the existing data which was a fresh unpack of the main snapshot which tried v1.0.2, v1.0.3, and v1.0.4. First time after on v.1.0.5 was repeating stage 5 over and over; restarted and now it's just stuck on [5/15 Bodies] No block bodies to write in this log period block number=28266663. Trying to unpack the snapshot again and start fresh on that and see

@zhy827827
Copy link

Our nodes often lag behind blocks,and restart erigon then erigon sync started again.
the issuse logs:
[5/15 Bodies] No block bodies to write in this log period block

/home/ubuntu/erigon/build/bin/erigon --datadir=/opt/bscdata/erigon --chain=bsc --db.pagesize=16k --torrent.download.rate=512mb --torrent.upload.rate=10mb --private.api.addr=127.0.0.1:9090 --http.api eth,erigon,web3,net,debug,trace,txpool --ws --ws.compression --http.addr=0.0.0.0 --http.corsdomain '*' --http.vhosts '*' --p2p.protocol=66,68 --torrent.download.slots 6 --bodies.cache 6341225472

@setunapo
Copy link
Collaborator

@zhy827827
Copy link

That's great

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants