Author: Wladimir 2014-08-13 20:29:28
Published on: 2014-08-13T20:29:28+00:00
In an email dated August 13th, 2014, a user named 潘庆庆 asked the Bitcoind community why '-flushwallet' is true by default. They had tried disabling it and found that their IO reduced greatly, but they also lost all of their coins in testnet after one crash. Wladimir explained that when flushwallet is disabled, the wallet is not flushed periodically, which means that there's a larger chance that the wallet database is in an inconsistent state when the process stops unexpectedly. This can happen either due to a crash or an external cause such as the power turning off unexpectedly. With the wallet in a non-self-contained state, the next time that you start bitcoind BerkeleyDB will have to process log files. There is a non-zero chance that this will fail, and manual recovery is needed. As the wallet is usually critical, it is unwise to disable that option.
Updated on: 2023-06-09T02:09:02.480395+00:00