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.

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

Retire xabi due to high disk utilisation rate and corrupt indices #1013

Merged
merged 1 commit into from
Nov 14, 2022

Commits on Nov 14, 2022

  1. Retire xabi due to high disk utilisation rate and corrupt indices

    `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 committed Nov 14, 2022
    Configuration menu
    Copy the full SHA
    bc66306 View commit details
    Browse the repository at this point in the history