DWQA QuestionsCategory: BlockchainDatabase compacting, degraded performance database for Ethernet workshop synchronization problem
pengttyy asked 2 years ago

In the process of synchronization in ETF, the following conditions occur in the log

INFO [11-24|12:29:51.925] Imported new block receipts              count=239  elapsed=2.543s    number=5234756 hash=4e45f1…933999 age=8mo2w3d  size=19.65mB
INFO [11-24|12:29:53.711] Imported new state entries               count=756  elapsed=5.585ms   processed=29283541 pending=2090 retry=0  duplicate=17 unexpected=88
INFO [11-24|12:29:54.395] Imported new block receipts              count=756  elapsed=2.452s    number=5235512 hash=fe3e9c…0bf05f age=8mo2w3d  size=60.57mB
WARN [11-24|12:29:56.523] Database compacting, degraded performance database=/mnt/blockstorage/ethereum-node/.ethereum/geth/chaindata
WARN [11-24|12:30:56.537] Database compacting, degraded performance database=/mnt/blockstorage/ethereum-node/.ethereum/geth/chaindata
WARN [11-24|12:31:56.559] Database compacting, degraded performance database=/mnt/blockstorage/ethereum-node/.ethereum/geth/chaindata
WARN [11-24|12:32:56.572] Database compacting, degraded performance database=/mnt/blockstorage/ethereum-node/.ethereum/geth/chaindata
WARN [11-24|12:33:56.585] Database compacting, degraded performance database=/mnt/blockstorage/ethereum-node/.ethereum/geth/chaindata

Have you ever met, please give me some advice!!!!

2 Answers
Lucas answered 2 years ago

Today, the upgrade of eth 1.8.20 also happened. After reboot, it will continue to synchronize data. But unfortunately, I encountered this problem again a few hours later. At present, I have not found a solution to this problem. In version 1.7.x, this has not happened. If there is a solution, please let me know.

necrophiliaboi answered 2 years ago

I met him, too, but it was just as good as it was when I was looking for a problem. If you can, let me tweet yzy335153329