Bitcoin full node and query server
Nov 3, 2024
View in context in the libbitcoin Slack #general mirror.
evoskuil22:08
Interestingly, Core took forever to shut down. over 5 minutes. This was a problem in BN in previous prototyping, like 5-7 years ago. In the current design, based on that experience of protracted shutdowns, we made a significant effort to ensure that nothing apart from the necessary mmap flush would delay stop. mmap flush on this machine can be significant, as there is 256GB of RAM that may need to be flushed. But with the current SSD I've never seen it go much past 1 minute, and usually much less (and it makes no difference what mode we are in, just the amount of unflushed RAM).
It appeared that BC validation continued after stop was signaled, maybe not wanting to discard the downloaded but not validated blocks. But the long indicated that the last block was updated before the shutdown was received and logged (matching the time that I noted it was signaled (minute 57)...
2024-11-03T21:57:03Z UpdateTip: new best=00000000000000000071ef0363647bbfb591b04ee268642060596ca21b7671d7 height=500298 version=0x20000000 log2_work=87.697860 tx=284383466 date='2017-12-20T18:03:47Z' progress=0.257010 cache=7979.4MiB(62457317txo) 2024-11-03T21:57:03Z opencon thread exit 2024-11-03T21:57:03Z Shutdown: In progress... 2024-11-03T21:57:03Z addcon thread exit 2024-11-03T21:57:03Z msghand thread exit 2024-11-03T21:57:03Z net thread exit 2024-11-03T21:57:03Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started 2024-11-03T21:57:03Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.00s) 2024-11-03T21:57:04Z scheduler thread exit 2024-11-03T21:57:04Z Writing 0 mempool transactions to file... 2024-11-03T21:57:04Z Writing 0 unbroadcast transactions to file. 2024-11-03T21:57:04Z Dumped mempool: 0.000s to copy, 0.005s to dump, 27 bytes dumped to file 2024-11-03T22:03:27Z Shutdown: done