Skip to content

Elasticsearch conflict when indexing is done against an elasticsearch cluster #362

@daniellienert

Description

@daniellienert
{
    "update": {
        "_index": "app-a7106994710190d3408cd8ae0aaff28e-1607503492",
        "_type": "_doc",
        "_id": "c63e218fd4d451f2e838fa8fa55c61a062750290",
        "status": 409,
        "error": {
            "type": "version_conflict_engine_exception",
            "reason": "[c63e218fd4d451f2e838fa8fa55c61a062750290]: version conflict, required seqNo [20278], primary term [1]. current document has seqNo [20281] and primary term [1]",
            "index_uuid": "6sJpuqx-RH-BBcwF6qUnwg",
            "shard": "0",
            "index": "app-a7106994710190d3408cd8ae0aaff28e-1607503492"
        }
    }
}

Could be that configuring the conflict handling helps (https://www.elastic.co/guide/en/elasticsearch/reference/7.9/docs-update-by-query.html#docs-update-by-query-api-query-params)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions