Skip to:

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

[BP of MB-52474]: [Upgrade] Timers handler stuck in deploying state after offline upgrade from 6.6.5 to 7.1.1

Description

STEPS

  1. Cluster consists of 5 nodes (2 kv, 1 eventing, index and query node each) running CB server 6.6.5-10080.

  2. Create the required set of buckets.

  3. Create 2 eventing functions - bucket op and timers.

  4. Deploy timer function.

  5. Perform offline upgrade of the cluster of 7.1.1-3115.

OBSERVATION
Timers handler is stuck in deploying state.

errors in eventing.log post upgrade

Also following set of log statements indicate internal undeployment was triggered for timers handler due to deletion of metadata collection.
Can confirm that there was no step involving deletion of metadata collection in the test so not sure how it was triggered.

NOTE
Issue is not reproducible consistently, test has ran into it only once.
PFA logs for eventing node.

Components

Affects versions

Fix versions

Labels

Environment

6.6.5-10080 7.1.1-3115

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

s3://cb-customers-secure/mb-52474/2022-06-08/172.23.106.73-20220607-2338-diag.zip

Release Notes Description

None

Activity

Show:

CB robot October 7, 2022 at 8:53 AM

Build couchbase-server-7.2.0-5000 contains eventing commit 2376a3f with commit message:
: Notify supervisor when producer is terminating

Sujay Gad July 13, 2022 at 6:15 AM

Test is passing for offline upgrade from 6.6.5-10080 to 7.1.2-3358.
Hence closing this ticket.

CB robot June 17, 2022 at 1:13 PM

Build couchbase-server-7.1.2-3313 contains eventing commit 2376a3f with commit message:
: Notify supervisor when producer is terminating

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 June 15, 2022 at 6:23 AM
Updated October 7, 2022 at 8:53 AM
Resolved June 17, 2022 at 10:52 AM
Instabug