Skip to content

Concurrency issue in elastic search #1090

@mfeurer

Description

@mfeurer

Elastic search sometimes fails stochastically with the error:

{"error":{"root_cause":[{"type":"version_conflict_engine_exception","reason":"[data][125]: version conflict, required seqNo [108522], primary term [1]. current document has seqNo [108523] and primary term [1]","index_uuid":"d_zNAG--SW-U97P61jOrSg","shard":"0","index":"data"}],"type":"version_conflict_engine_exception","reason":"[data][125]: version conflict, required seqNo [108522], primary term [1]. current document has seqNo [108523] and primary term [1]","index_uuid":"d_zNAG--SW-U97P61jOrSg","shard":"0","index":"data"},"status":409}

on calling https://test.openml.org/api/v1/xml/data/untag

According to @joaquinvanschoren this is due to https://stackoverflow.com/questions/64034453/elastic-search-version-conflict-issue

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions