You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
Proposal
Here is a simple version of the proposal to resolve the two problems:
Additional Context
No response
The text was updated successfully, but these errors were encountered: