You are viewing a single comment's thread from:
RE: Test - Create/Edit Op Status
Hello @steemchiller
I have tested fullnode i deployed, and most of the interfaces seem to be normal. But when call get_ account_ History or et_accounts api , there is a high probability that the following errors will be reported (5 out of 10 times have problems).
Error : Unable to acquire database lock rpcerror: unable to acquire database lock.
Do you have any solutions? Thank you.
Hi, the database locks occur while data is being written to the database. So I guess the write process takes too long when syncing the database with the blockchain on your server (which happens constantly). I only use high speed SSDs (NVMe) on my servers and it works without any problems so far.
Do you use a high speed disk like SSD or HDD?
I think what you said is the key reason. According to my observation, when the block time offset exceeds 2000ms. This error is more likely to occur
Now, after the block time offset is less than 1000ms. The problem doesn't seem to be happening anymore。
I am currently using a high-speed HDD.If this problem often occurs, I may have to upgrade my hardware. Thank you again for your help！