My node always showing 100 blocks behind #258
Comments
|
Better hardware, nvme required. |
|
I am using the better hardware, with 8 vCPU 32 GB of RAM and 5GB of Bandwidth and SSD 3000 IOPS. Please let me know if I need to increase this. |
|
3000 IOPS is nothing. A typical NVME SSD is doing around 250000 - 500000 IOPS |
|
I am using AWS kindly please let me know which type of disk I need to use. And as per my understanding we are using nvme type of SSD in aws. |
|
Just because they're selling you an NVME doesn't mean that you are getting all of that power. |
|
My node has been 60~100 blocks behind for more than a week. Also the below syncing result on my node can give you an idea the lower boundary of # of knownStates, as of 2021-05-27. Update: please check out how I finally synced with a different instance type in comment |
|
@DefiDebauchery I have increased my IOPS to 16k, and I am hoping it will be synced asap. @bencao do you know how much |
|
update gp3 IOPS to 16k too...hope some improve |
Yes I've changed the disk type to gp3 and IOPS is 16k, but still the known state is behind, and I don't know how much time this is gonna take. As I am trying to sync it from last 2 weeks. And this is making me really sick. As I also downloaded the snapshot I thought that will work but I don't see any help on that too, as currently I am syncing BSC on two instance one with snapshot and other one without snapshot. |
I have the same problem ...T_T IOPS 16k help nothing... |
|
same issue here. Just followed the recommended instance type.
|
|
Is this repo has contributors or not, I don't see anyone want to help us to resolve this issue. |
|
I had an AWS Update 1Some raw numbers to check during syncing:
expand to see details
expand to see detailsUpdate 2Finally synced in 10 hours!
expand to see detailsUpdate 3I'll share my AWS EC2 based configuration here hope that can help others struggling with building a fully synced node. 1. EC2 Instance ConfigI used a When the instance first started you have to create file system on the 900G blk device by 2. /opt/bsc/node/config.toml3. /etc/systemd/system/geth.service4. chain initialization stepsUpdate 4CostAccording to AWS Pricing Calculator, the cost for a Caveats
|
|
I'm using However, the sync has never been slow. and I used this snapshot to get the initial data. Please note. |
|
@seonggwonyoon your syncing is completed? Can you please let us know the highest knownStates you know. |
|
@urkishan Yes sync is completed. |
|
Seonggwon Yoon - If eth.syncing shows that json object, your node is not
sync'd
…On Fri, May 28, 2021 at 9:36 AM Seonggwon Yoon ***@***.***> wrote:
@urkishan <https://github.com/urkishan> Yes sync is completed.
{
currentBlock: 7803509,
highestBlock: 7803510,
knownStates: 297473485,
pulledStates: 297473485,
startingBlock: 7803508
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#258 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGIZ4IHSJTOKMCFXYPMDVTTP6L5PANCNFSM45RKYXIA>
.
|
|
@n8twj Thank you for letting me know json object returns false, but it stops syncing for a while to see the knownStates and print it. |
|
if you are seeing a json object that means your node is not staying in sync
- need faster IO. Make sure you are not running the OS and blockchain
data on the same drive. In fact do not use the NVMe SSD for anything else
than the blockchain data/geth
…On Fri, May 28, 2021 at 11:45 AM Seonggwon Yoon ***@***.***> wrote:
@n8twj <https://github.com/n8twj> Thank you for letting me know but, json
object returns false, but it stops syncing for a while to see the
knownStates and print it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#258 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGIZ4KERSGKYNXWB2CLBEDTP63BJANCNFSM45RKYXIA>
.
|
|
@urkishan @bgdsh @x1957 @seonggwonyoon Good news! Node synced in 10 hours. Details posted in the above comment |
|
@bencao thanks, synced using i3.xlarge |
|
Thank you @bencao, as one of the node of mine is also synced. Here is the details of AWS instance: With disk
Disk type: |
which type of nvme disk? gp2,gp3,io2? |
|
@x1957 it is |
|
@bencao first thanks a lot for your sharing and i follow all the steps that you describe and now is many day and i dont have full sync i have this result : { |
BSC node sync test report of AWS EC2Note: Region is Asia Pacific(Tokyo)
Note: sync take time calc from BSC node startup to log Note: Note: Note: Note: Hope this report will help others who want to setup a BSC node on AWS EC2. thanks @bencao |
|
/usr/local/bin/geth --rpc --ws |
|
Looks like that you forgot to init with Init is required at the first time, command example: geth --datadir /path/to/data/bsc-node init /etc/bsc/genesis.jsonThen run command begin to sync: geth --config /etc/bsc/config.toml --datadir /path/to/data/bsc-node consoleNote: |
|
@bencao 哥们帮忙看一下 |
|
@muyinliu Can't sync, always 100 blocks slow who can help me？ |
Show me the specification of your machine, please. It looks like that you are NOT using native NVMe SSD(PCIe 3.0×4 or higher) |
|
@muyinliu i3.xlarge aws ec2 |
|
@muyinliu 哥们留个wx 或者q 可以吗 谢了 |
|
Shared IO will NEVER SYNC. Get dedicated hardware.
On Fri, Jul 23, 2021 at 06:41 SatanBtc ***@***.***> wrote:
@muyinliu <https://github.com/muyinliu> i3.xlarge aws ec2
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#258 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGIZ4LHS4H3ZUYJTQCOWODTZFBNDANCNFSM45RKYXIA>
.
--
Typos courtesy of my iPhone...
|
|
@n8twj I am having the same issue. I have been syncing for about 16 hours and its always about 100 block behind. { |
|
Not even remotely fast enough to sync. You can try starting from a
snapshot but even then “get faster hardware”.
On Fri, Jul 30, 2021 at 00:58 SatanBtc ***@***.***> wrote:
I am having the same issue. I have been syncing for about 16 hours and its
always about 100 block behind.
ec2
i3.xlarge
@bencao <https://github.com/bencao> @muyinliu
<https://github.com/muyinliu> @n8twj <https://github.com/n8twj>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#258 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGIZ4MMWN5KNPI7CNYAH7LT2IWONANCNFSM45RKYXIA>
.
--
Typos courtesy of my iPhone...
|
|
why is this issue closed when a lot of people are experiencing the same thing? nodes that were synced in before are suddenly lagging. |
|
I have 12 core, 64g ram and 1T nvme ssd and still have this issoue. thats to tell u its not a hardware thing |
Yes, i guess the connected peer could be the issue. As when i try, it seems only able to connect 1 peer, which cause the syncing process slow. As this is P2P network, i think the more nodes it can connect the faster it could be. So, if it can connect more peers, i believe it can be faster. So updating the BootstrapNodes and StaticNodes may help more instead of paying x2 on buying the expensive SSD hard drive. How do we get the latest and stable node address? |
|
Found something here: https://ethereum.stackexchange.com/a/87931/76294
|
|
I restarted my BSC node, and I experience the same, always behind by ~houndred blocks... Does anyone have any idea what's going on? |
|
Make sure you have updated to 1.1.4 and have enabled diffsync, that seems
to help those servers who may not have the latest generation of NVMe drives.
|
Hi, I'm on 1.1.4, could you help me with this diffsync? On https://geth.ethereum.org/docs/interface/command-line-options I cannot see such a switch to enable :\ Update: |
|
this is not Ethereum yo......check this repo for equivalent docs... and/or
see release notes from 1.1.3
…On Fri, Nov 12, 2021 at 2:43 AM izidorit ***@***.***> wrote:
Make sure you have updated to 1.1.4 and have enabled diffsync, that seems
to help those servers who may not have the latest generation of NVMe drives.
Hi, I'm on 1.1.4, could you help me with this diffsync? On
https://geth.ethereum.org/docs/interface/command-line-options I cannot
see such a switch to enable :\
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#258 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGIZ4OA2VASJOP34NVPTWLULTARDANCNFSM45RKYXIA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Tried it: /usr/bin/geth --config /root/.ethereum/BSC-config.toml --diffsync --cache 131072 Still ~100 blocks away :( |
|
It is going to stay ~100 blocks away until/if it syncs up.
On Fri, Nov 12, 2021 at 03:24 izidorit ***@***.***> wrote:
Make sure you have updated to 1.1.4 and have enabled diffsync, that seems
to help those servers who may not have the latest generation of NVMe drives.
Tried it: /usr/bin/geth --config /root/.ethereum/BSC-config.toml
--diffsync --cache 131072
Still the same:
{
currentBlock: 12580876,
highestBlock: 12580994,
knownStates: 752010831,
pulledStates: 751997306,
startingBlock: 12574756
}
{
currentBlock: 12580943,
highestBlock: 12581009,
knownStates: 752129783,
pulledStates: 752109410,
startingBlock: 12574756
}
{
currentBlock: 12581007,
highestBlock: 12581084,
knownStates: 752818157,
pulledStates: 752805094,
startingBlock: 12574756
}
{
currentBlock: 12581071,
highestBlock: 12581148,
knownStates: 753455415,
pulledStates: 753442809,
startingBlock: 12574756
}
Still ~100 blocks away :(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#258 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGIZ4LV5KSLCEZFGOKAIK3ULTFLJANCNFSM45RKYXIA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Typos courtesy of my iPhone...
|
Sad fact, the same machine one month ago did the sync around 8 hours. Yesterday it started to fall back by 10-20 blocks, which caused slowness to the clients, who were using the node. Thus I removed geth folder, inited again, and started sync again...and it's not done after 34 hours, which is a pain in the ass... |
|
@izidorit keeps showing pending state entries by any chance did you update your geth client to 1.1.4 I suspect people who have synced are probably running an old client |
it would work? |
> eth.syncingIs there any way to boostup the syncing?
The text was updated successfully, but these errors were encountered: