Node cannot keep up to sync

Issue Report

My node keep online but the log shows it behind the best a lot.

Environment

  • Operating System: Ubuntu 18.04
  • Pulsar/Advanced CLI/Docker: CLI

Problem

best: #1630450 (0xc3da…4981), finalized #1537521
The finalized number is behind the best number with a big gap.
Can I got reward in this situation?
What can I do to make my node keep up the best number?

2024-05-22T22:17:01.224668Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630443 (0x0f10…f766), finalized #1537521 (0xff18…cd98), ⬇ 17.3kiB/s ⬆ 16.3kiB/s    
2024-05-22T22:17:01.394018Z  INFO Consensus: substrate: ✨ Imported #1630444 (0x52fe…0b57)    
2024-05-22T22:17:06.226075Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630444 (0x52fe…0b57), finalized #1537521 (0xff18…cd98), ⬇ 10.1kiB/s ⬆ 12.6kiB/s    
2024-05-22T22:17:07.598602Z  INFO Consensus: substrate: ✨ Imported #1630445 (0x4db9…85a1)    
2024-05-22T22:17:08.502581Z  INFO Consensus: substrate: ✨ Imported #1630445 (0x0dce…74b3)    
2024-05-22T22:17:09.205633Z  INFO Consensus: sc_informant: ♻️️  Reorg on #1630445,0x4db9…85a1 to #1630446,0x4de8…cf48, common ancestor #1630444,0x52fe…0b57    
2024-05-22T22:17:09.205702Z  INFO Consensus: substrate: ✨ Imported #1630446 (0x4de8…cf48)    
2024-05-22T22:17:11.226625Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630446 (0x4de8…cf48), finalized #1537521 (0xff18…cd98), ⬇ 17.7kiB/s ⬆ 12.4kiB/s    
2024-05-22T22:17:16.226950Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630446 (0x4de8…cf48), finalized #1537521 (0xff18…cd98), ⬇ 5.5kiB/s ⬆ 6.2kiB/s    
2024-05-22T22:17:19.387852Z  INFO Consensus: substrate: ✨ Imported #1630447 (0x64be…7f8a)    
2024-05-22T22:17:21.227284Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630447 (0x64be…7f8a), finalized #1537521 (0xff18…cd98), ⬇ 7.4kiB/s ⬆ 10.7kiB/s    
2024-05-22T22:17:26.234807Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630447 (0x64be…7f8a), finalized #1537521 (0xff18…cd98), ⬇ 9.9kiB/s ⬆ 10.7kiB/s    
2024-05-22T22:17:31.235277Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630447 (0x64be…7f8a), finalized #1537521 (0xff18…cd98), ⬇ 10.5kiB/s ⬆ 14.9kiB/s    
2024-05-22T22:17:33.049055Z  INFO Consensus: substrate: ✨ Imported #1630448 (0xc7f5…b682)    
2024-05-22T22:17:36.236239Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630448 (0xc7f5…b682), finalized #1537521 (0xff18…cd98), ⬇ 15.9kiB/s ⬆ 9.6kiB/s    
2024-05-22T22:17:41.236680Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630448 (0xc7f5…b682), finalized #1537521 (0xff18…cd98), ⬇ 6.3kiB/s ⬆ 7.1kiB/s    
2024-05-22T22:17:46.237015Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630448 (0xc7f5…b682), finalized #1537521 (0xff18…cd98), ⬇ 6.9kiB/s ⬆ 8.9kiB/s    
2024-05-22T22:17:46.649733Z  INFO Consensus: substrate: ✨ Imported #1630449 (0x3f49…7756)    
2024-05-22T22:17:51.237514Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630449 (0x3f49…7756), finalized #1537521 (0xff18…cd98), ⬇ 11.7kiB/s ⬆ 9.0kiB/s    
2024-05-22T22:17:56.238134Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630449 (0x3f49…7756), finalized #1537521 (0xff18…cd98), ⬇ 4.3kiB/s ⬆ 5.7kiB/s    
2024-05-22T22:17:56.459949Z  INFO Consensus: substrate: ✨ Imported #1630450 (0xc3da… 4981)    
2024-05-22T22:18:01.239054Z  INFO Consensus: substrate: 💤 Idle (6 peers), best: #1630450 (0xc3da…4981), finalized #1537521 (0xff18…cd98), ⬇ 7.1kiB/s ⬆ 10.9kiB/s
1 Like

It is supposed to be this way, there is absolutely no problem to solve here.