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

Tracking Issue: accelerate recover speed #800

Closed
1 of 2 tasks
ShiKaiWi opened this issue Mar 31, 2023 · 0 comments
Closed
1 of 2 tasks

Tracking Issue: accelerate recover speed #800

ShiKaiWi opened this issue Mar 31, 2023 · 0 comments
Labels
feature New feature or request

Comments

@ShiKaiWi
Copy link
Member

ShiKaiWi commented Mar 31, 2023

Describe This Problem

Current mechanism of recovering when starting up costs too much time when the number of tables belonging to the ceresdb server instance is large. And there are two known reasons accounting for the slow recovering:

  • Recovering work is processed table by table, but data is actually organized by shard;
  • Recovering work is handled in the same runtime with write work, that is to say, recovering work has intensive contention with the writing work.

Proposal

Here is a simple version of the proposal to resolve the two problems:

Additional Context

No response

@ShiKaiWi ShiKaiWi added the feature New feature or request label Mar 31, 2023
@ShiKaiWi ShiKaiWi pinned this issue Mar 31, 2023
@ShiKaiWi ShiKaiWi changed the title Tracing Issue: accelerate recover speed Tracking Issue: accelerate recover speed Mar 31, 2023
@tanruixiang tanruixiang unpinned this issue Jul 21, 2023
@ShiKaiWi ShiKaiWi closed this as completed Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant