Skip to:

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

DCP client with { or } in the name doesn't log DCP messages in memcached log

Description

Observed that the kafka DCP connector connected, created a DCP producer and associated streams, yet none of this activity was logged.

This occurs because the DCP name chosen includes "{" and "}" and that fails to log

This is an issue for 6 and 7 but appears fixed in 7.1

Components

Affects versions

Fix versions

Labels

Environment

None

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

None

Release Notes Description

None

Activity

Show:

Praneeth Bokka March 28, 2022 at 3:15 PM

Verified with Enterprise Edition 7.1.0 build 2534 and we can see the Kafka DCP logs now:

Ritam Sharma November 12, 2021 at 9:09 AM

 - Can one of your team member validate it from Kafka.

Dave Rigby November 5, 2021 at 1:29 PM

"Fixed" in Neo (the code in that area has changed and the '{' is escaped correctly). Resolving as this doesn't meet the criteria for backporting to previous releases.

Dave Rigby October 18, 2021 at 11:25 AM

Bumping to major - for the versions which this affects; does cause issues in understanding what the DCP client is doing.

Jim Walker September 29, 2021 at 11:21 AM

Fine in 7.1 (neo checked 7.1.0-1378)

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

Details

Assignee

Reporter

Is this a Regression?

Unknown

Triage

Triaged

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created September 29, 2021 at 8:19 AM
Updated September 3, 2024 at 9:51 PM
Resolved November 5, 2021 at 1:29 PM
Instabug