Skip to:

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

[BP to 7.2.0] - Panic in NodeTable::Get - Logging improvements

Description

panic on 6.6.2-9588-1:

 

panic on 7.0.0-5302-1:

 

 

It appears that there is a nil value in the NodeTable. Must also add asserts in NodeTable to catch this.

Components

Affects versions

Fix versions

Labels

Environment

None

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

None

Release Notes Description

None

Activity

Show:

Varun Velamuri March 29, 2023 at 7:19 AM

Closing this on dev-verification based on the steps mentioned in above comment

Varun Velamuri March 29, 2023 at 7:19 AM

Verified the logging change using instrumented code (By explicitly setting nil value to list.Head) and the below error messages are seen as expected

CB robot February 16, 2023 at 12:00 AM

Build couchbase-server-7.2.0-5178 contains indexing commit c7a7eeb with commit message:
[BP]: Log nil values in NodeTable

CB robot February 15, 2023 at 3:36 PM

Build couchbase-server-7.2.0-5176 contains indexing commit abf8174 with commit message:
Add more logging when inserting nil value into back store

Varun Velamuri February 15, 2023 at 1:16 PM
Edited

Verified the issue by instrumenting a nil head insertion and validated the logs.

- I have merged GSI side changes. Please merge memdb side changes and resolve the issue. Thanks!

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

Details

Assignee

Reporter

Is this a Regression?

No

Triage

Untriaged

Due date

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created January 29, 2023 at 3:44 PM
Updated August 31, 2024 at 11:06 AM
Resolved February 16, 2023 at 5:42 AM
Instabug