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

Inconsistent timestamps in query.log

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 4.5.0
    • 4.1.0
    • query
    • Security Level: Public
    • Untriaged
    • Unknown

    Description

      MB-14161 was created to make all logging have consistent (ISO-8601) timestamps.

      In query.log I found the following examples:

      2015-12-08T18:53:22.691+00:00 [Warn] node 3 status: "unhealthy"
      		 
      2015-12-16T13:16:04.909+00:00 [Info] connected with 1 indexers
      		 
      2015/12/16 13:16:38 Warning: Finalizing a bucket with active connections.

      As far as I can see, the indexing project has its own logging module which does the correct formatting.

      The "Finalizing a bucket" message also appears in the go-couchbase project, which uses the default golang "log" module which does not use the correct formatting.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-14161 Time format should be consist across all components: ISO_8601

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

          Task - A task that needs to be done. MB-17071 goport logging is not in the correct timestamp format.

          • Major - Major loss of function.
          • Open
          For Gerrit Dashboard: MB-17094
          # Subject Branch Project Status CR V
          59759,2 MB-17094 Inconsistent timestamps in query.log master go-couchbase Status: MERGED +2 +1
          59760,1 MB-17094 Inconsistent timestamps in query.log master gomemcached Status: MERGED +2 +1

          Activity

            People

              Sitaram.Vemulapalli Sitaram Vemulapalli
              malarky Chris Malarky
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty