jayakasadev opened a new pull request, #67502:
URL: https://github.com/apache/doris/pull/67502

   ### What problem does this PR solve?
   
   Issue Number: close #67458
   
   Related PR: N/A
   
   Problem Summary:
   
   * writes are rejected with `TOO_MANY_VERSION` errors when a tablet has too 
many versions. The code checks `_approximate_num_rowsets`, but its not emitted 
as a metric. 
   * `tablet_version_num_distribution` is similar, but it updates less 
frequently and skips tablets that are currently being written to
   * added `tablet_approximate_num_rowsets_distribution` which uses 
`_approximate_num_rowsets` and includes active tablets
     * allows users to create alerts before getting `TOO_MANY_VERSION` errors
   
   ### Release note
   
   Add `tablet_approximate_num_rowsets_distribution` for cloud-mode tablet 
version-limit monitoring
   
   ### Check List (For Author)
   
   - Test
       - [x] Unit Test
           - Added 
`CloudTabletMgrTest.TestApproximateRowsetsMetricIncludesActiveTablets`.
       - [x] Manual test
           - `build-support/clang-format.sh`
           - `build-support/check-format.sh`
           - `build-support/check-build-hygiene.sh`
           - `git diff --check`
   
   - Behavior changed:
       - [x] Yes.
           - Cloud BEs expose the new 
`tablet_approximate_num_rowsets_distribution` Prometheus histogram.
   
   - Does this need documentation?
       - [x] No.
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to