Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
7.1.0
-
None
-
Untriaged
-
1
-
Unknown
Description
indexer.log is currently covering less than 24 hours as in the log MB-50557. Few top logging statements were removed to avoid more logging. We can further optimise the per vbucket prints by accumulating the state and printing periodically or etc. Prints to StreamBegin, StreamEnd, SystemEvent and etc can use such logging.
Logging this bug to improve logging to have the log data of around one week as requested in MB-50557
Todo:
- Reduce per vbucket prints in various places
- Check if these messages can be converted to stat and dumped periodically
- Or If we have some event based logging rather than logging for all vbucket.
Attachments
Issue Links
- relates to
-
MB-50557 Indexing.log covers less than 24hours
- Closed