Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
idjemaoune opened this issue Jan 24, 2025 · 1 comment
Open

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

idjemaoune opened this issue Jan 24, 2025 · 1 comment

Comments

@idjemaoune
Copy link

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-<collection_name>)

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)

@idjemaoune
Copy link
Author

The Solr backup process is asynchronous when using the API call for backups:

The parameter async=search-engine-s3-backup-comment (which represents the request ID) is always the same. This causes the first backup to succeed, but subsequent backups fail, stating that the request ID already exists. When i use the backup endpoint wihtout async params the backups work as expected (incremental)

curl -u admin:admin "http://search-engine-solrcloud-common.freeze:8983/solr/admin/collections?action=BACKUP&&collection=comment&location=%2F&maxNumBackupPoints=1&name=search-engine-s3-backup-comment&repository=search-engine-backups-freeze&wt=json"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant