Skip to content

CNDB-12716: Metric for writes blocked on memory allocation#2279

Open
MSpryszynski wants to merge 1 commit intomainfrom
cndb-12716
Open

CNDB-12716: Metric for writes blocked on memory allocation#2279
MSpryszynski wants to merge 1 commit intomainfrom
cndb-12716

Conversation

@MSpryszynski
Copy link

What is the issue

We should know whenever writes get blocked due to memory shortage in the memtable.
CC already has a Timer metric, MemtablePool::blockedOnAllocating. However, the problem with a Timer metric is that it is only updated once the timed event ends. I.e. when the writes are unblocked.

What does this PR fix and why was it fixed

Added counter metric for writes blocked on allocation to be able to see spikes of blocked allocations immediately

* Added counter metric for writes blocked on allocation to be able to see spikes of blocked allocations immediately
@github-actions
Copy link

Checklist before you submit for review

  • This PR adheres to the Definition of Done
  • Make sure there is a PR in the CNDB project updating the Converged Cassandra version
  • Use NoSpamLogger for log lines that may appear frequently in the logs
  • Verify test results on Butler
  • Test coverage for new/modified code is > 80%
  • Proper code formatting
  • Proper title for each commit staring with the project-issue number, like CNDB-1234
  • Each commit has a meaningful description
  • Each commit is not very long and contains related changes
  • Renames, moves and reformatting are in distinct commits
  • All new files should contain the DataStax copyright header instead of the Apache License one
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants