-
Notifications
You must be signed in to change notification settings - Fork 184
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
I built my own node one today has not been able to catch up with the latest height #2746
Comments
same here always out of sync |
+1 |
same here always out of sync |
no matter with hardware, just the network issue |
Same issue. CPU and RAM peak due to this issue too. |
Same issue. even after pulling the new version and running the repair-state. Slow syncing |
try this if you are using leveldb: exchaind start
--pruning everything
--chain-id exchain-66
--mempool.sort_tx_by_gp
--iavl-enable-async-commit=true
--iavl-cache-size=10000000
--mempool.recheck=0
--mempool.force_recheck_gap=2000
--disable-abci-query-mutex=1
--mempool.size=200000
--mempool.max_gas_used_per_block=120000000
--home /data_folder/
--disable-abci-query-mutex=1
--fast-query=1
--enable-bloom-filter=1 if you are using rocksdb exchaind start
--pruning everything
--chain-id exchain-66
--db_backend rocksdb
--mempool.sort_tx_by_gp
--iavl-enable-async-commit=true
--iavl-cache-size=10000000
--mempool.recheck=0
--mempool.force_recheck_gap=2000
--disable-abci-query-mutex=1
--mempool.size=200000
--mempool.max_gas_used_per_block=120000000
--home /data_folder/
--disable-abci-query-mutex=1
--fast-query=1
--enable-bloom-filter=1 Switching to rocksdb is recommended as leveldb will no longer be maintained |
@sing1ee thanks for the response, I tried the commands above and still my node is slow syncing. im using rocksdb and the version 1.6.5.1 as well. |
https://t.me/XENCryptoTalk/367273 In my personal opinion, this was caused by the wrong gas policy. the gas limit of the block was even increased. and the gas price cannot be adjusted correctly, https://www.oklink.com/en/okc/block/15416037 the execution pressure of the block during this period is too high, causing most nodes to take a long time to sync the state. There are some ways to help you sync faster:
But these may not help much. Just let the nodes to sync, even if it will be very slow. |
same issue from 17/11, who can help |
I have tried, but it seems to be getting slower, only 30 blocks are synchronized in 10 minutes |
@sing1ee The gas limit of the block is now 120 million, which I think is still too high. there is a lot of 'scripted' XEN minting with very low gas price in each block. |
same problem here, using rocksdb and the iavl flags mentioned in this discussion |
Hi, @stepollo2 , If you run node as rpc, please start exchaind:
if you run node as validator, please start exchaind:
We benifit from improve our disk‘s iops(16000) and throughput(1000M). Hope it helps. |
Here
Here are the details requested:
Snippet from the logs:
|
Hi @stepollo2 ,
Version is OK
Is that your machine has the memory problem? I saw you set
the workload is pretty heavy. BTW, how is your machine's configuration? |
I anyway updated the binaries to latest release. exchaind currently runs on sdc
Disks are 14TB SSDs. I have the possibility to test on another machine with 7TB NVMEs drives |
Since the gas incident happened, I've never been able to run the node again. I'm pretty sure that nothing is wrong with hardware here: 2TB NMVe and 64 GB RAM machine |
Hi @stepollo2 , do you run the node as rpc or validator? |
Hi @dandavid3000 ,
Could you please provide exhaind's version information?
Could you provide the exchaind's start command? do you run the node as rpc, validator or archive node?
This machine seems good enough. Is your node runs on cloud service provider? If so please check the disk's IOPS and throughput |
I run the node for RPC only |
Hi @stepollo2 ,
Let's drop the flag |
Dropped already but is not helping much :/ |
Hi @stepollo2 ,
|
@stepollo2 I recommend you to use the latest snapshot for syncing https://static.okex.org/cdn/oec/snapshot/index.html The height you are currently synchronizing is when the block is most congested, and each block will consume hundreds of millions of gas, the synchronization will definitely be slow. |
@dandavid3000 Can you provide a few lines of the node log for the latest height? |
I ran the node on a local PC.
I tested multiple times with different exchaind. The latest one is v1.6.5.10 and mainnet-s0-fss-20221127-15594367-rocksdb.tar.gz Start cmd
|
Could you use the latest data snapshot mainnet-s0-fss-20221205-15769737-rocksdb.tar.gz it will help to sync.
If you run your node as validator, you should set --node-mode=val, if you run node as rpc, we'd better use s1 data. mainnet-s1-fss-20221204-15764063-rocksdb.tar.gz
how to install tcmalloc with OKC:
|
Thanks for your help. I confirmed that the node is working well on my side.
|
version:1.6.5.1
ubuntu20.04
The text was updated successfully, but these errors were encountered: