Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
6.6.2, 7.0.0, 6.6.3, 7.0.2, 7.0.1
-
None
-
Triaged
-
1
-
Unknown
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
Attachments
Issue Links
- causes
-
JDCP-206 Change DCP name to avoid Data Service issues
-
- Resolved
-
For Gerrit Dashboard: MB-48655 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
162902,2 | JDCP-206 Change DCP name to avoid Data Service issues | master | java-dcp-client | Status: MERGED | +2 | +1 |
Activity
Field | Original Value | New Value |
---|---|---|
Link | This issue is caused by CBSE-10781 [ CBSE-10781 ] |
Assignee | Daniel Owen [ owend ] | Jim Walker [ jwalker ] |
Summary | Kafka connector doesn't log expected DCP messages in memcached log | 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.
The observed behaviour was very much as if it triggered the following FTS 'suppression' code that is present in 6.6.x https://github.com/couchbase/kv_engine/blob/v6.6.3/engines/ep/src/dcp/producer.cc#L211-L224 * We do not see any {{logger->log}} messages * We do see some EP_LOG_WARN/EP_LOG_INFO messages (which are not subject to the suppression. Yet all observable information about the connection's DCP name suggests this clause should not have triggered. * From stats.log the producer's name does not contain {{eq_dcpq:fts}} which the code states is the search string (not copied the producer name here as it contains PII) |
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 |
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 |
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 |
Affects Version/s | 7.0.1 [ 17104 ] | |
Affects Version/s | 7.0.0 [ 17233 ] | |
Affects Version/s | 6.6.2 [ 17103 ] | |
Affects Version/s | 7.0.2 [ 18012 ] |
Link |
This issue causes |
Priority | Minor [ 4 ] | Major [ 3 ] |
Fix Version/s | Neo [ 17615 ] |
Triage | Untriaged [ 10351 ] | Triaged [ 10350 ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Assignee | Jim Walker [ jwalker ] | Arunkumar Senthilnathan [ arunkumar ] |
Link | This issue is triggering CBSE-11257 [ CBSE-11257 ] |
Link | This issue relates to CBSE-11255 [ CBSE-11255 ] |
Link | This issue blocks CBSE-10897 [ CBSE-10897 ] |
Assignee | Arunkumar Senthilnathan [ arunkumar ] | Praneeth Bokka [ praneeth.bokka ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Reproduce with 6.6.3 and the following name
eq_dcpq:{"i":"540AA7A2EA8ED9FE/D6558E4C4AA86D91","a":"kafka-connector/4.0.6 (test-couchbase-source) java-dcp-client/0.34.0 Java/17 (Homebrew; OpenJDK 64-Bit Server VM; 17+0) OS (Mac OS X; 10.15.7; x86_64)"}
I see no stream request messages, but do have a connector and some backfill messages (logged with EP_LOG_INFO)