to use invalidateblock "hash" I have to wait processing blocks on disk ends, which is the point to process blocks what I dont want to?
invalidateblock when processing blocks on disk #18978
issue mrbabtc opened this issue on May 15, 2020-
mrbabtc commented at 12:02 AM on May 15, 2020: none
- mrbabtc added the label Bug on May 15, 2020
-
maflcko commented at 12:08 AM on May 15, 2020: member
What are the steps to reproduce this bug?
- maflcko closed this on May 15, 2020
-
mrbabtc commented at 1:16 PM on May 15, 2020: none
What are the steps to reproduce this bug?
sync the node, restart it deleting chainstate folder(or use -rescan-chainstate maybe could work too) and it will process the blocks on disk, now you have no way no stop it without closing it, invalidateblock should stop this process but it waits to process all the blocks before taking action
- maflcko reopened this on May 15, 2020
-
promag commented at 10:20 AM on May 17, 2020: member
-rescan-chainstate
you mean
-reindex-chainstate.Problem is that RPC server is in warmup and doesn't process RPC requests. I don't think this should change because of a developer only RPC.
-
mrbianchi commented at 3:24 PM on May 19, 2020: none
-rescan-chainstate
you mean
-reindex-chainstate.Problem is that RPC server is in warmup and doesn't process RPC requests. I don't think this should change because of a developer only RPC.
i agree but maybe isn't hard fix that
- maflcko removed the label Bug on May 19, 2020
- maflcko added the label Feature on May 19, 2020
- maflcko added the label RPC/REST/ZMQ on May 19, 2020
-
pinheadmz commented at 5:09 PM on March 7, 2023: member
@mrbianchi is this still an issue for you? I'm curious why you would want to cancel reindex? What can you do with your node in that state?
-
maflcko commented at 5:19 PM on March 7, 2023: member
Closing for now
- maflcko closed this on Mar 7, 2023
- bitcoin locked this on Mar 6, 2024
