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

background ledger close: implement concurrent database access #4319

Open
Tracked by #4128
anupsdf opened this issue May 14, 2024 · 0 comments · May be fixed by #4533
Open
Tracked by #4128

background ledger close: implement concurrent database access #4319

anupsdf opened this issue May 14, 2024 · 0 comments · May be fixed by #4533
Assignees

Comments

@anupsdf
Copy link
Contributor

anupsdf commented May 14, 2024

No description provided.

@marta-lokhova marta-lokhova changed the title background ledger close: concurrent database access. Switch to using connection pools, so ledger close and things like publishing and peer management can run concurrently. A few observations here background ledger close: implement concurrent database access May 14, 2024
@marta-lokhova marta-lokhova self-assigned this Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants
@marta-lokhova @anupsdf and others