Skip to:

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

ClusterChangeMapNotification reported in logs and errors instead of KV ops

Description

Seeing messages in the logs like:

The 'ClusterMapChangeNotification' in this case is really a KV GET or SET I believe, especially since this is a 7.2.4 cluster and there shouldn't be any ClusterMapChangeNotification's till running against 7.6.

It also gets reported in the CouchbaseException.message if the KV op fails as 

 

Full logs for this 7.2 run:

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Attachments

1

Activity

Show:

Jeffry Morris March 13, 2024 at 10:29 PM
Edited

In turns out this is a minor logging bug. The server uses both the opcode and the magic bit to determine the operation type. Both SET and ClustermapChangeNotification share the same opcode 0x01; they differ in the magic bit: 0x08 vs 0x82. When the logger tries to log the request before it gets fired off, it uses the OpCode enum which uses the last occurence of an enum's values name. 

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

Details

Assignee

Reporter

Story Points

Fix versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created March 13, 2024 at 5:39 PM
Updated March 14, 2024 at 3:54 PM
Resolved March 14, 2024 at 3:54 PM
Instabug