Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.5.1, 6.6.0
-
Component/s: couchbase-bucket
-
Story Points:1
Description
In MB-28468 (5.5.x) the log level for FTS connections to memcached was reduced, to prevent the overly-noisy logging from wrapping the memcached logs too soon.
This is fixed with improvements in CC/7.0, and the logging has been re-enabled in memcached.
In the meantime however (6.5/6.6), we have no way of debugging the DCP streams for problematic FTS index builds.
Please add a mechanism to allow the re-enabling of logs from FTS for this purpose - default should be the same behaviour.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue relates to CBSE-8571 [ CBSE-8571 ] |
| Fix Version/s | 6.6.1 [ 17002 ] |
| Link | This issue blocks MB-40563 [ MB-40563 ] |
| Assignee | Daniel Owen [ owend ] | Ben Huddleston [ ben.huddleston ] |
| Due Date | 23/Jul/20 |
| Fix Version/s | 6.6.0 [ 16787 ] |
Could do one of two things here.
- Create a config variable to disable the blacklist of FTS connection logging. This would treat FTS connections in the same way as any other.
- Create a config variable to set the FTS connection log level explicitly. This may make debugging easier as the FTS connections could be set to a debug level without setting the reset of the memcached process to a debug level.
They're both about the same amount of work.
| Fix Version/s | 6.6.1 [ 17002 ] |
| Labels | logging supportability | approved-for-6.6.0 logging supportability |
| Link | This issue blocks MB-38724 [ MB-38724 ] |
Fix merged to kv_engine/6.5.1 branch (for 6.5.1-MP2).
Add a new config option:
- dcp_blacklist_fts_connection_logs - Blacklists FTS DCP logging by
default by setting the log level to critical and unregistering the
logger from log level verbosity changes. Defaults to true.
To un-blacklist FTS, change this to false.
Usage:
Set either via bucket config, or epctl on a per node / per bucket basis:
cbepctl <HOST> -u Administrator -p asdasd -b <BUCKET> set dcp_param dcp_blacklist_fts_connection_logs false
| Assignee | Ben Huddleston [ ben.huddleston ] | Chris Malarky [ malarky ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Validated on 6.5.1-6302 and 6.6.0-7897.
memcached logs have logs entries like the below ones after un-blacklisting FTS connection logs
memcached.log.000004.txt:2020-07-24T14:29:31.029040-07:00 INFO 758: (default) DCP (Producer) eq_dcpq:fts:social_234ec66318275839_f4e0a48a-33d8da21 - (vb:206) ActiveStream::transitionState: Transitioning from backfilling to in-memory
|
memcached.log.000004.txt:2020-07-24T14:29:31.431235-07:00 INFO 758: (default) DCP (Producer) eq_dcpq:fts:social_234ec66318275839_f4e0a48a-33d8da21 - (vb:226) Backfill complete, 11357 items read from disk, 638 from memory, last seqno read: 47582, pendingBackfill : False
|
memcached.log.000004.txt:2020-07-24T14:29:31.456859-07:00 INFO 758: (default) DCP (Producer) eq_dcpq:fts:social_234ec66318275839_f4e0a48a-33d8da21 - (vb:226) ActiveStream::transitionState: Transitioning from backfilling to in-memory
|
memcached.log.000004.txt:2020-07-24T14:29:32.062066-07:00 INFO 758: (default) DCP (Producer) eq_dcpq:fts:social_234ec66318275839_f4e0a48a-33d8da21 - (vb:216) Backfill complete, 11326 items read from disk, 643 from memory, last seqno read: 95680, pendingBackfill : False
|
memcached.log.000004.txt:2020-07-24T14:29
|
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Link | This issue blocks MB-42583 [ MB-42583 ] |
| Fix Version/s | 6.5.2 [ 17223 ] |
| Labels | approved-for-6.6.0 logging supportability | approved-for-6.6.0 logging releasenote supportability |
Daniel Owen is there going to be some setting/configuration that will allow re-enabling of logs from FTS ?