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
Is your feature request related to a problem? Please describe.
Background
We hope to give a interface to know how many compactor node we need to scale to speed up our compactor.
So it is important to know how much data need to be compacted to make the LSM tree balanced.
However, it is difficult to know this. Because the shape of this tree is changing dynamically. We can not know the accurate number.
The only thing we can know is that, for the current shape of the LSM tree, how much data we need to compact the next level (Compacting to next level does not mean that we can make the LSM tree balanced). If the size is too large we need to scale more compactor-node at once. So we will give an imprecise reference value, which will be less than the actual amount of resources currently required.
Is your feature request related to a problem? Please describe.
Background
We hope to give a interface to know how many compactor node we need to scale to speed up our compactor.
So it is important to know how much data need to be compacted to make the LSM tree balanced.
However, it is difficult to know this. Because the shape of this tree is changing dynamically. We can not know the accurate number.
The only thing we can know is that, for the current shape of the LSM tree, how much data we need to compact the next level (Compacting to next level does not mean that we can make the LSM tree balanced). If the size is too large we need to scale more compactor-node at once. So we will give an imprecise reference value, which will be less than the actual amount of resources currently required.
Design
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: