apache / apache/solr-operator

Issue: Backup Fails Due to Duplicate Request ID (S3 bucket)

Open
#753 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Go
Stars
283
Forks
148
PR merge metrics
No merged PRs in 30d

Description

When creating a SolrBackup Kubernetes object, it successfully performs the first backup and creates a backup for each collection in the S3 bucket. However, after the first backup, subsequent backups fail with the following error:
org.apache.solr.common.SolrException: Task with the same requestid already exists. (search-engine-backup-)

I want to backup a collection named comment :

INFOS: `org.apache.solr.common.SolrException: Task with the same requestid already exists. (search-engine-s3-backup-comment)`

INFO: `2025-01-24 12:30:35.768 INFO (qtp1613627715-23-search-engine-solrcloud-1.freeze.svc.cluster.local-1032) [c:comment s: r: x: t:search-engine-solrcloud-1.freeze.svc.cluster.local-1032] o.a.s.s.HttpSolrCall [admin] webapp=null path=/admin/collections params={async=search-engine-s3-backup-comment&maxNumBackupPoints=15&name=search-engine-s3-backup-comment&action=BACKUP&location=/&collection=comment&repository=search-engine-backups-freeze&wt=json} status=400 QTime=11`

ERROR: `2025-01-24 12:30:45.844 ERROR (qtp1613627715-20-search-engine-solrcloud-1.freeze.svc.cluster.local-1033) [c:comment s: r: x: t:search-engine-solrcloud-1.freeze.svc.cluster.local-1033] o.a.s.h.RequestHandlerBase Client exception => org.apache.solr.common.SolrException: Task with the same requestid already exists. (search-engine-s3-backup-comment)`

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file or test is named. Start by tracing the SolrBackup reconciliation for the Solr /admin/collections BACKUP request shown, then reproduce with the `comment` collection and compare request IDs across the first and later backups. Done means subsequent backups complete without the duplicate-request-ID error and create the expected S3 backups.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go, kubernetes
Domain
databases, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.