Skip to content

Refresh .security index before/after migrations #110562

Open

Description

.security index migrations (of which there's currently a single instance, but there are plans for more) should ideally be preceded and/or succeeded by a refresh operation.
Without a preceding refresh, docs that should've been migrated might be missed.
Similarly, without following a given migration by a refresh, any subsequent migration might experience docs version conflicts, or APIs relying on migrated docs might temporarily (until the next automatic refresh) return wrong results (e.g. the query roles API querying roles on metadata after a migration without a refresh will erroneously return empty results).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions