Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-21062

[CX] ensure log messages have appropriate severity (Vulcan)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 5.5.0
    • CBAS DP
    • analytics
    • None
    • Untriaged
    • Unknown
    • CX Sprint 31, CX Sprint 32, CX Sprint 33, CX Sprint 34, CX Sprint 35, CX Sprint 36, CX Sprint 37, CX Sprint 38, CX Sprint 39, CX Sprint 97, CX Sprint 98

    Description

      There are various messages in red-service.log with LOG LEVEL SEVERE  like:
      		 
       
      		 
      SEVERE: Attempting to stop org.apache.hyracks.api.lifecycle.LifeCycleComponentManager@6d8a00e3
      		 
       
      		 
      SEVERE: Stopping component instanceorg.apache.asterix.transaction.management.service.locking.ConcurrentLockManager dump state false dump path null
      		 
       
      		 
      But these seem to be normal messages and there is nothing SEVERE about these log messages.
      		 
      This is confusing.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-29402 [CX] Some log messages have inadequate severity

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-29114 [CX] ensure log messages have appropriate severity (Alice)

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-28860 "Adding a config node" is displayed with log level ERRO in analytics logs

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. MB-27314 Configure out of box log level of Analytics to WARN

          • Major - Major loss of function.
          • Closed
          For Gerrit Dashboard: MB-21062
          # Subject Branch Project Status CR V
          91715,6 MB-21062, MB-28860: log severity fixes vulcan analytics-dcp-client Status: MERGED +2 +1
          91848,1 MB-21062, MB-28860: log severity fixes master analytics-dcp-client Status: ABANDONED 0 -1
          92007,3 MB-21062: incremental improvements in log levels vulcan analytics-dcp-client Status: MERGED +2 +1
          92063,3 MB-21062: minimize info logs on dropped channels vulcan analytics-dcp-client Status: MERGED +2 +1
          92203,3 More MB-21062, fix timeout to be 60s, not 600000s vulcan asterix-opt Status: MERGED +2 +1

          Activity

            People

              michael.blow Michael Blow
              Prerna.Manaktala Prerna Manaktala (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 3h
                  3h
                  Remaining:
                  Remaining Estimate - 3h
                  3h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified

                  Gerrit Reviews

                    There are no open Gerrit changes

                    PagerDuty