Uploaded image for project: 'Couchbase Lite'
  1. Couchbase Lite
  2. CBL-5346

Logging Replicator reasons of state change

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Major
    • Beryllium
    • Beryllium
    • LiteCore
    • Security Level: Public
    • None

    Description

      In addition to seeing the following logs when replicator changes state,

         [Sync]: {Puller#357} {Coll#0} now busy

      We would like to see reason for debugging purpose, like "(_caughtUp=0)" in the following 

          [Sync]: {Puller#357} {Coll#0} state now busy (_caughtUp=0)

       

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            jianmin.zhao Jianmin Zhao
            jianmin.zhao Jianmin Zhao
            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