Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to acquire database lock error occurs frequently #234

Open
ety001 opened this issue Jul 4, 2022 · 0 comments · May be fixed by #235
Open

Unable to acquire database lock error occurs frequently #234

ety001 opened this issue Jul 4, 2022 · 0 comments · May be fixed by #235
Assignees

Comments

@ety001
Copy link
Member

ety001 commented Jul 4, 2022

Due to the lack of performance tuning of RocksDB, the current ahnode api performance is seriously insufficient.

Now we have set redis cache to -2 (cached without expiration only if it is irreversible in terms of blockchain consensus) for get_ops_in_block and get_transaction api except the get_account_history api.

But lots of get_account_history(username, -1, 10000) requests pass through ahnode.
The large range query will seriously slow down ahnode performance because locks are frequently generated.
That's why the steemitwallet.com is not stable in this two weeks.
The wallet service and ahnode apis are deeply coupled. When the ahnode api goes down, the wallet will give out a 504 error.

So we plan to reduce the get_account_history limit from 10000 to 100 in jussi layer. That means get_account_history api from official api will only return up to 100 pieces of data.

The change will take effect at 2022-07-06 13:00:00 (UTC+8) .

@ety001 ety001 self-assigned this Jul 4, 2022
@ety001 ety001 linked a pull request Jul 6, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant