Retire xabi due to high disk utilisation rate and corrupt indices
#1013
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`xabi` is the latest STH-backed indexer node that's suffering from: * corrupt indices, which results in volatile find response latency, and * high disk utilisation growth with no obvious link to ingest rate. The node has now fully utilised its 60Ti PVC, with the index growth of 14Ti over the last couple of days alone. This behaviour was observed in other STH-backed instances; see #826. Remove the node, considering the index records stored by the node are present by other healthy nodes, its corrupt indices and 100% disk utilisation at 60Ti (that is close to the 64Ti limit for io2 volumes).
masih
requested review from
gammazero and
willscott
and removed request for
gammazero
willscott
approved these changes
Nov 14, 2022
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1013 +/- ##
==========================================
- Coverage 55.14% 55.09% -0.05%
==========================================
Files 120 120
Lines 11412 11412
==========================================
- Hits 6293 6288 -5
- Misses 4433 4436 +3
- Partials 686 688 +2
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
xabiis the latest STH-backed indexer node that's suffering from:The node has now fully utilised its 60Ti PVC, with the index growth of 14Ti over the last couple of days alone. This behaviour was observed in other STH-backed instances; see #826.
Remove the node, considering the index records stored by the node are present by other healthy nodes, its corrupt indices and 100% disk utilisation at 60Ti (that is close to the 64Ti limit for io2 volumes).