BUG - node stuck syncing #11796975 downloading blocks after i changed account_id in ~/.near/betanet/validator_key.json

[dirmansebastian]

Describe the bug or test
Version: 1.11.0-beta.1, Build: 75d156f8-modified

My validator seby05.betanet is online 0% and not producing blocks:

My node was synchronized , then i changed account_id in ~/.near/betanet/validator_key.json from seby05 to seby05.betanet, same as deployed accountId staking contract.

How to Reproduce
Steps to reproduce the behavior:
1.nearup stop
2. nano ~/.near/betanet/validator_key.json, edit account_id
3.nearup betanet --nodocker

Expected behavior OR Outcome of test
To not sync the whole chain from 0, old data remain the same....history is history, cannot be changed , why i should sync the whole chain again?

Now my node it's stuck syncing #11796975 downloading blocks ...
Aug 19 20:43:11.334 INFO stats: #11796975 Downloading blocks **99%** V/97 16/16/40 peers ⬇ 698.5kiB/s ⬆ 118.0kiB/s 0.00 bps 0 gas/s CPU: 121%, Mem: 1.0 GiB

Sometimes Aug 19 20:45:37.135 INFO stats: #11796975 Downloading headers **100%** V/97 16/16/40 peers ⬇ 596.8kiB/s ⬆ 63.2kiB/s 0.00 bps 0 gas/s CPU: 117%, Mem: 1.1 GiB

Specs (please complete the following information):

• OS:Ubuntu 18.04
• Which cloud / on-premise: cloud
• CPU: Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
• RAM: 8GB
• Disk space: 200GB

Additional context
Add any other context about the problem here.

Screenshots Optional

[bowenwang1996]

that is expected. You need to delete data and resync in this case because you don't have the state information to begin with. To avoid this issue, you can change tracked_shards in your config.json to [0].