More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Elasticsearch ILM Rollover Alias Split

    1

    Fix ambiguous write aliases after an Elasticsearch rollover partial failure

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Elasticsearch ILM Rollover Alias Split

    Repair Elasticsearch ILM Rollover Alias Split

    Example session with this skill installed

    Two indices claim the write alias while ILM cannot advance.

    Available evidence: index alias state (partial). Additional evidence requested: state and configuration snapshot, error and recovery logs, deployment and alert timeline. Review the case, identify open evidence gaps, and do not invent a live test or production change.

    • Read your context and instructions
    • Compiled the repair elasticsearch ilm

    Repair Elasticsearch ILM Rollover Alias Split — EVIDENCE-LIMITED REVIEW

    Scenario received

    Two indices claim the write alias while ILM cannot advance.

    Source register

    • S1: index alias state — PARTIAL SOURCE PROVIDED.
    • S2: state and configuration snapshot — NOT PROVIDED; REQUIRED TO VERIFY.
    • S3: error and recovery logs — NOT PROVIDED; REQUIRED TO VERIFY.
    • S4: deployment and alert timeline — NOT PROVIDED; REQUIRED TO VERIFY.

    Concrete checks

    1. inspect ILM history and write-index flags — PRELIMINARY, NOT VERIFIED.
    2. validate alias correction and rollback conditions — AWAITING CORROBORATING EVIDENCE.
    3. crosscheck source timestamps identifiers and changed versions — AWAITING CORROBORATING EVIDENCE.
    4. record exceptions and reversible verification gates — AWAITING CORROBORATING EVIDENCE.

    Deliverables / acceptance gates

    • index alias state evidence map: DRAFT / INCOMPLETE until evidence is validated.
    • alias split exception register: DRAFT / INCOMPLETE until evidence is validated.
    • one writer validation plan: DRAFT / INCOMPLETE until evidence is validated.

    Decision

    INCOMPLETE — HUMAN REVIEW REQUIRED. Confirm dates, IDs, affected scope, owners and acceptance evidence. Do not claim authorization or execution that did not occur.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Elasticsearch Index Lifecycle Management (ILM) failures often leave clusters in a broken state where multiple indices claim the same write alias. This skill identifies the root cause of rollover splits and generates the precise administrative actions needed to restore a single writer.

    What it does

    • Alias state mapping creates a clear map of which indices are currently competing for the write alias.
    • ILM history inspection analyzes lifecycle logs to find the exact point of partial failure or timeout.
    • Validation planning generates a step-by-step plan to remove invalid flags and re-point the alias.
    • Exception registration logs timestamped contradictions between index metadata and expected ILM states.

    How it works

    1. Analyze logs by reviewing index alias states, ILM history, and deployment timelines provided in the context.
    2. Classify evidence using a disciplined framework to mark observations as VERIFIED, CONTRADICTED, or UNVERIFIED.
    3. Generate recovery plan producing a bounded set of commands to fix the alias split without losing data.

    Frameworks & tools

    Specific to Elasticsearch and OpenSearch clusters using ILM or ISM policies. It requires local text exports of index settings, alias configurations, and cluster health logs.

    Why this beats prompting it yourself

    Manual recovery from alias splits is high-risk and often leads to split-brain indexing or data loss. This skill enforces a strict evidence-led discipline that separates inferences from raw log data before suggesting any destructive alias changes.

    Use cases

    • Fix "multiple indices found for alias" errors during rollover.
    • Resolve ILM stay-in-place stalls where the write index flag is duplicated.
    • Audit cluster state after a failed manual intervention on a lifecycle policy.

    Known limitations

    Requires local text-based logs or state snapshots. It cannot directly connect to live clusters or execute API calls autonomously.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Data & Databases.

    Cannot verify inaccessible environments or data not supplied. Missing or contradictory evidence must be marked INCOMPLETE or UNVERIFIED. Owner approval is required for operational or compliance decisions.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 20 days ago

    Permissions

    Read Files

    Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.

    Listed20 days ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill resolves the 'split-brain' alias state where multiple Elasticsearch indices mistakenly claim the write flag simultaneously, causing ILM rollovers to stall or fail.

    It is designed for any AI agent that supports text-based context; simply provide your index settings and ILM logs as input to get a structured recovery plan.

    No direct cluster access is required; you simply export your cluster's alias and ILM state as text and provide it to the agent for analysis.

    You receive the logic framework for alias state mapping, the ILM history inspection protocol, and a guided process for generating safe recovery commands.

    This skill uses a 'VERIFIED/CONTRADICTED' evidence framework that prevents the agent from making guesses, ensuring that suggested commands are based strictly on your log data to prevent data loss.

    Yes, while optimized for Elasticsearch ILM, the logic framework is fully compatible with OpenSearch Index State Management (ISM) configurations.

    New in Data & Databases