Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Internal Server error is raised while performing backup on a index node using cbbackupmgr

Description

Steps to reproduce -

1. Create a KV bucket, scope and collection named
Bucket Name - ojnEcQ_e%h6PSTcISl_-5-219000
Scope Name - ewjmBK-5-220000
Collection Name - 19t9piCEahGf8mn-5-220000
2. Create dataset on the above created collection.
3. Use following cbbackupmgr commands to create a backup -

A similar issue was observed for backup API which was fixed - https://couchbasecloud.atlassian.net/browse/MB-45724

Components

Affects versions

Fix versions

Labels

Environment

Enterprise Edition 7.0.0 build 5295

Link to Log File, atop/blg, CBCollectInfo, Core dump

https://cb-jira.s3.us-east-2.amazonaws.com/logs/MB-46895/collectinfo-2021-06-14T151438-ns_1%4010.112.205.101.zip https://cb-jira.s3.us-east-2.amazonaws.com/logs/MB-46895/collectinfo-2021-06-14T151438-ns_1%4010.112.205.102.zip

Release Notes Description

None

Attachments

1

Activity

Show:

Hemant Rajput November 19, 2021 at 9:30 AM

Validated on 7.1.0-1695

Was able to successfully take backup on indexer node.

 

 

 

CB robot June 21, 2021 at 3:15 PM

Build couchbase-server-7.1.0-1030 contains indexing commit 8d1cc77 with commit message:
: Internal Server error is raised while performing backup on a index node using cbbackupmgr

Carlos Gonzalez Betancort June 16, 2021 at 11:01 AM

I believe the interface we agreed on for backups of collections was /api/v1/bucket/<bucket name>/backup?include=<collections/scopes list> or exclude with the same format (include and exclude a mutually exclusive).

For reference the design doc for collection restore/backup -> https://docs.google.com/document/d/1NVvSFC_enKQU0C-eQ6NXoYaNQ90VXY5jN8RqMahvnr8/edit#heading=h.b7iqwqesg1v2

and Please let me know if I am wrong about that.

Carlos Gonzalez Betancort June 15, 2021 at 6:10 AM

Looking at the backup logs I can see it dispatches the correct request (path escaped) to the indexer node:

But it seems like we get a 500 from the indexer. In the indexer logs I can see the following:

Seeing how the bucket is part of the REST path I think this may be an issue with indexer I tried to reproduce with other bucket/scope/collection name that also had '%' in the names but it worked but when trying with the specific names provided it failed.

Could someone in the indexer team have a look at why this could be?

Umang Agrawal June 14, 2021 at 3:51 PM

Please find attached the cbbackmgr logs -

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Is this a Regression?

No

Triage

Untriaged

Operating System

Centos 64-bit

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created June 14, 2021 at 3:18 PM
Updated November 19, 2021 at 9:30 AM
Resolved June 22, 2021 at 4:54 AM
Instabug