v0.202.20016 Node always reports 2-5 slots behind - never fully catches up #3493
-
Running a v0.202.20016 on a AMD EPYC 9374F 32-Core Processor The UI reports the node as always 2-5 slots behind. I am using the following layout - what changes if any should be done so that the node reports 0,1 behind. [layout] --- lscpu output -- Architecture: x86_64 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
netwoking problems or some of the tiles backpressuring? |
Beta Was this translation helpful? Give feedback.
-
Hello @bkaria, I apologize for the late reply. Being up to 3 slots behind is expected during normal operation. The more stake you have, the sooner you receive block data from other Solana validators. Thus, unstaked nodes tend to lag behind by a bit. Network latency also plays a factor. I hope you have been able to try out the latest Frankendancer version. Please let us know if you see any improvements with this version. |
Beta Was this translation helpful? Give feedback.
Hello @bkaria, I apologize for the late reply. Being up to 3 slots behind is expected during normal operation. The more stake you have, the sooner you receive block data from other Solana validators. Thus, unstaked nodes tend to lag behind by a bit. Network latency also plays a factor. I hope you have been able to try out the latest Frankendancer version. Please let us know if you see any improvements with this version.