Skip to content
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

reset command took almost two hours to begin #1101

Open
pinheadmz opened this issue Oct 10, 2022 · 1 comment
Open

reset command took almost two hours to begin #1101

pinheadmz opened this issue Oct 10, 2022 · 1 comment

Comments

@pinheadmz
Copy link
Member

This node was almost fully synced but I wanted to replay Taproot activation so I called reset 709600. The command took almost TWO HOURS to work:

[D:2022-10-10T02:10:02Z] (chaindb) Removing alternate chain: 00000000000000000003692560991d576c4ebc7ea0fb8a96079bf7d9ab6d8ee4.
[D:2022-10-10T02:10:02Z] (chaindb) Resetting main chain to: 00000000000000000001c65a327b00e28ec2a7cf6e9952fe8ce34b3278395ee4

...


[D:2022-10-10T04:15:37Z] (chain) Memory: rss=368mb, js-heap=76/118mb native-heap=249mb
[I:2022-10-10T04:15:37Z] (chain) Block 000000000000000000012762ba7d5d929f839403c62a1c80ffe42ef09c5393a9 (709601) added to chain (size=128320 txs=336 time=144.864725).
@pinheadmz
Copy link
Member Author

Update: chain may actually be undoing blocks during this time, there's just no logging in the for(;;) loop inside chaindb.reset()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant