Skip to:

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

[Upgrade] dcp_stream_boundary remains as "from_prior" after upgrade

Description

The UI and REST endpoints will give mixed messages until the first lifecycle operation

CB server - 6.6.1 - 9213
create and deploy handler having "dcp_stream_boundary": "everything".
pause and resume handler.
"dcp_stream_boundary" will become "from_prior".
Upgrade cluster to 7.0.0 - 5177
"dcp_stream_boundary" remains as "from_prior"

 

Components

Affects versions

Fix versions

Labels

Environment

None

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

None

Release Notes Description

None

Activity

Sujay Gad August 20, 2021 at 11:58 AM

Verified using 7.0.2 - 6547.

Stats before upgrade -

Stats after upgrade -

CB robot August 13, 2021 at 9:15 AM

Build couchbase-server-7.1.0-1140 contains eventing commit 144c54b with commit message:
: Replace 'from_prior' while writing out from store

CB robot August 13, 2021 at 5:36 AM

Build couchbase-server-7.0.2-6503 contains eventing commit ccf27f9 with commit message:
: Replace 'from_prior' while writing out from store

Ritam Sharma July 16, 2021 at 11:26 AM

- This definitely needs to be taken care for upgrade. Thank you, please add it to 7.0.1

Jeelan Poola July 12, 2021 at 6:00 AM

This needs to be fixed in 7.0.1 for better user experience post upgrade. Request inclusion in 7.0.1. Thank you!

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

Details

Assignee

Reporter

Is this a Regression?

Unknown

Triage

Untriaged

Operating System

Centos 64-bit

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created May 18, 2021 at 6:56 AM
Updated August 20, 2021 at 11:58 AM
Resolved August 13, 2021 at 5:27 AM
Instabug