weaviate/weaviate · error

could not get replication operation details by collection an

Error message

could not get replication operation details by collection and shards: %w

What it means

Returned by the RAFT store's Query handler when GetReplicationDetailsByCollectionAndShard fails for a TYPE_GET_REPLICATION_DETAILS_BY_COLLECTION_AND_SHARD request; replication operation details for that collection/shard pair could not be retrieved.

Source

Thrown at cluster/store_query.go:152

	case cmd.QueryRequest_TYPE_GET_NAMESPACES:
		payload, err = st.namespaceManager.Get(req)
		if err != nil {
			return &cmd.QueryResponse{}, fmt.Errorf("could not get namespaces: %w", err)
		}
	case cmd.QueryRequest_TYPE_GET_REPLICATION_DETAILS:
		payload, err = st.replicationManager.GetReplicationDetailsByReplicationId(req)
		if err != nil {
			return &cmd.QueryResponse{}, fmt.Errorf("could not get replication operation details: %w", err)
		}
	case cmd.QueryRequest_TYPE_GET_REPLICATION_DETAILS_BY_COLLECTION:
		payload, err = st.replicationManager.GetReplicationDetailsByCollection(req)
		if err != nil {
			return &cmd.QueryResponse{}, fmt.Errorf("could not get replication operation details by collection: %w", err)
		}
	case cmd.QueryRequest_TYPE_GET_REPLICATION_DETAILS_BY_COLLECTION_AND_SHARD:
		payload, err = st.replicationManager.GetReplicationDetailsByCollectionAndShard(req)
		if err != nil {
			return &cmd.QueryResponse{}, fmt.Errorf("could not get replication operation details by collection and shards: %w", err)
		}
	case cmd.QueryRequest_TYPE_GET_REPLICATION_DETAILS_BY_TARGET_NODE:
		payload, err = st.replicationManager.GetReplicationDetailsByTargetNode(req)
		if err != nil {
			return &cmd.QueryResponse{}, fmt.Errorf("could not get replication operation details by target node: %w", err)
		}
	case cmd.QueryRequest_TYPE_GET_SHARDING_STATE_BY_COLLECTION:
		payload, err = st.replicationManager.QueryShardingStateByCollection(req)
		if err != nil {
			return &cmd.QueryResponse{}, fmt.Errorf("could not get sharding state by collection: %w", err)
		}
	case cmd.QueryRequest_TYPE_GET_SHARDING_STATE_BY_COLLECTION_AND_SHARD:
		payload, err = st.replicationManager.QueryShardingStateByCollectionAndShard(req)
		if err != nil {
			return &cmd.QueryResponse{}, fmt.Errorf("could not get sharding state by collection and shard: %w", err)
		}
	case cmd.QueryRequest_TYPE_GET_REPLICATION_SCALE_PLAN:
		payload, err = st.replicationManager.QueryReplicationScalePlan(req)

View on GitHub (pinned to 75aa4b6d11)

Solutions

  1. Inspect the wrapped error for the concrete cause
  2. Verify the collection/shard pair is correct and exists
  3. Retry once the replication op for that shard settles
Defensive patterns

Strategy: retry

When it happens

Trigger: Thrown at cluster/store_query.go:152 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of weaviate/weaviate@75aa4b6d11 (2026-09-04). Data as JSON: /api/errors/20efaab1842db97b. Report an issue: GitHub.