Skip to:

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

[BP MB-49720 to 7.0.4] - Rollback handling - Retry with previous uuid on rollback message

Description

On kv node failure, DCP consumer may not be able to resume from where it left.
DCP producer asks DCP consumer to rollback to certain sequence number and history since requested vbucket history won't be available on failed kv node. In this scenario, DCP consumer will rollback to 0 and eventing will start stream from 0.
Starting stream from 0 can be avoided in certain situation by retrying stream with previous vbucket history.

Components

Affects versions

None

Fix versions

Labels

Environment

None

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

None

Release Notes Description

None

Activity

Sujay Gad April 21, 2022 at 10:36 AM

Validated the fix on Enterprise Edition 7.0.4 - 7261.

CB robot April 7, 2022 at 1:05 PM

Build couchbase-server-7.0.4-7244 contains eventing commit 189cc30 with commit message:
https://couchbasecloud.atlassian.net/browse/MB-51379#icft=MB-51379: Store failover log in checkpoint blob

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

Details

Assignee

Reporter

Is this a Regression?

Unknown

Triage

Untriaged

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created March 11, 2022 at 2:08 AM
Updated April 21, 2022 at 10:36 AM
Resolved April 7, 2022 at 1:02 PM
Instabug

Flag notifications