[Gracefully stopping] Unable to Stop a node When OldReceipts are in progress and bunch of new block are to be downloaded

[kamilchodola]

Describe the bug Mainnet synced until OldReceipts and during OldReceipts node has been stopped. After one day of waiting, node is restarted and there are 10k blocks to be downloaded and OldReceipts still Inprogress. When both of those operations are in progress, I'm unable to CTRL + C to stop a node. No Keyboard action is reflected on console.

Expected behavior Possibility to stop a node in controlled way.

Desktop (please complete the following information):

• Windows11

[kamilchodola]

@brbrr Can You please retest that? Do you have a Windows machine?

[brbrr]

@kamilchodola I do not have a windows machine, unfortunately.

[brbrr]

yup, confirming, it's not closing the process:

07 Mar 21:39:39 | Old Receipts  1,289,475 / 19,384,619 (  6.65 %) | queue    18,994 | current           13 Blk/s | total          767 Blk/s
07 Mar 21:39:42 | Closing, please wait until all functions are stopped properly...
07 Mar 21:39:42 | Stopping session monitor...
07 Mar 21:39:42 | Stopping session sync mode selector...
07 Mar 21:39:42 | Sync mode selector stopped
07 Mar 21:39:42 | Stopping discovery app...
07 Mar 21:39:42 | Stopping block producer...
07 Mar 21:39:42 | Stopping sync peer pool...
07 Mar 21:39:42 | Stopping discovery udp channel
07 Mar 21:39:42 | Discovery shutdown complete.. please wait for all components to close
07 Mar 21:39:44 | Old Receipts  1,299,495 / 19,384,619 (  6.70 %) | queue    12,620 | current        2,000 Blk/s | total          771 Blk/s
07 Mar 21:39:48 | Received new block:  19385738 (0x5a36fd...460e48)
...

Next consecutive CTRL-C combinations have no effect on the process.

UPD:

It did shut down the node after some time:

07 Mar 21:42:28 | All done, goodbye!

[kamilchodola]

It is still concerning - took quite a lot of time to shutdown process (3 minutes as I see)

It was processing blocks in meantime (catching up after downtime)?

[brbrr]

yeah, I've re-ran the node, and it recovered and was progressing with sync and over night it ran out of disk space.

Here are the logs, just in case: https://gist.githubusercontent.com/brbrr/71aecb51d3cc3e7f25e95e81e93de7ea/raw/16b3841b40eab720ca8292eb33fd9798ab29ce3c/mainnet.log