Uploaded image for project: 'Couchbase Python Client Library'
  1. Couchbase Python Client Library
  2. PYCBC-484

timeout logging is too verbose at LCB_LOGLEVEL=1

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • .backlog3.x
    • 2.4.0-beta
    • None
    • None
    • 1

    Description

      With the attached script (on my system) the attached output with tracing enabled ends up logging three times. Two ERRORs and a WARN for each timeout. That seems a bit excessive.

      Also, isn't LCB_LOGLEVEL=1 intended as just ERROR level?

      I simply ran it as:
      LCB_LOGLEVEL=1 python timeoutme.py > run.out 2>&1

      Attachments

        1. timeoutme.py
          0.6 kB
        2. run.out
          2 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            jared.casey Jared Casey
            ingenthr Matt Ingenthron
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty