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.

Sign up for GitHub

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

Jump to bottom

Split/merge is case of an OVERLOADED datatashard #11849

Open
azevaykin opened this issue Nov 21, 2024 · 2 comments
Open

Split/merge is case of an OVERLOADED datatashard #11849

azevaykin opened this issue Nov 21, 2024 · 2 comments
Assignees
@ijon

Comments

@azevaykin
Copy link
Collaborator

OVERLOADED error is returned by a datashard if:

  1. The partition is not in a normal state, for example, it is being divided/merged.
  2. The input queue of transaction is full (more than 15,000 requests).
  3. The CDC output queue is full (more than 10,000 items or 125 MB).

System view partition_stats has already had counters like InFlightTxCount, TxRejectedByOverload. These metrics can be taken into consideration for split/merge.
@kunga
Copy link
Member

kunga commented Nov 21, 2024

Connected with https://st.yandex-team.ru/KIKIMR-20199

@kunga
Copy link
Member

kunga commented Nov 21, 2024 •
edited
Loading

Maybe DataShard itself should request split without passing dozens of metrics to SchemeShard

And we need a UI button to do the same (split DataShard on request)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ijon ijon

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ijon @kunga @azevaykin