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

Optimize api.db on cluster #1361

Closed
goshawk-3 opened this issue Apr 5, 2022 · 1 comment · Fixed by #1393
Closed

Optimize api.db on cluster #1361

goshawk-3 opened this issue Apr 5, 2022 · 1 comment · Fixed by #1393
Assignees

Comments

@goshawk-3
Copy link
Contributor

goshawk-3 commented Apr 5, 2022

Describe the bug
It turns out that api.db is growing fast in size on any cluster node. We should find a way to clean it up on regular base to avoid wasting disk space.

 1.2G Apr  5 09:53 /opt/dusk/dusk_data/chain/api.db
@goshawk-3 goshawk-3 self-assigned this Apr 5, 2022
@goshawk-3
Copy link
Contributor Author

As per findings, this database stores full provisioners (+stakes) data per each round. We should record provisioners and their stakes only on a change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant