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

XDCR : Replication rate has regressed in build 4.5.0-1798.

    XMLWordPrintable

Details

    • Untriaged
    • Yes

    Description

      Replication rate has regressed in build 4.5.0-1798.

      • 1 x 1, non-DGM (100M)
        4.5.0-1770 : 96K items / sec
        4.5.0-1798 : 42K items / sec.

      All other tests also regressed.

      Attachments

        Issue Links

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

          Activity

            wayne Wayne Siu added a comment -

            Verified in 4.5.0-1939.

            wayne Wayne Siu added a comment - Verified in 4.5.0-1939.
            wayne Wayne Siu added a comment -

            Build 4.5.0-1939 (back to go 1.5) seems to have addressed the regression in replication rate.
            MB-18185 is still open to track the slight regression from go 1.5.

            wayne Wayne Siu added a comment - Build 4.5.0-1939 (back to go 1.5) seems to have addressed the regression in replication rate. MB-18185 is still open to track the slight regression from go 1.5.
            ritesh.motlani Ritesh Motlani (Inactive) added a comment - - edited

            I was not able to reproduce these bugs locally with golang 1.6 version.
            but running golang race detector shows problem of "Data Race" Condition on the code as show in the attaced logs.
            so fix would be put locks on settingMap & registryMap and that should fix the problem of goxdcr crashing.
            I hope that should also fix the performance problem but need to test it out.

            -Thanks
            RItesh

            ritesh.motlani Ritesh Motlani (Inactive) added a comment - - edited I was not able to reproduce these bugs locally with golang 1.6 version. but running golang race detector shows problem of "Data Race" Condition on the code as show in the attaced logs. so fix would be put locks on settingMap & registryMap and that should fix the problem of goxdcr crashing. I hope that should also fix the performance problem but need to test it out. -Thanks RItesh

            This issue occurs with go 1.6 . I have not been able to reproduce locally ..
            I am working on reproducing this issue on dev sanity.

            -THanks
            Ritesh

            ritesh.motlani Ritesh Motlani (Inactive) added a comment - This issue occurs with go 1.6 . I have not been able to reproduce locally .. I am working on reproducing this issue on dev sanity. -THanks Ritesh

            Hi Ritesh, will this be addressed today/tomorrow? Thanks.

            keshav Keshav Murthy added a comment - Hi Ritesh, will this be addressed today/tomorrow? Thanks.

            It seems like on 1798 build, goxdcr is crashing couple of times and getting restarted. Restarting goxdcr leads to processing of mutation from the beginning every time goxdcr re-start.

            GOXDCR is crashing at statistic manager service due to race condition. I still working on finding solution.

            -Thanks
            Ritesh

            ritesh.motlani Ritesh Motlani (Inactive) added a comment - It seems like on 1798 build, goxdcr is crashing couple of times and getting restarted. Restarting goxdcr leads to processing of mutation from the beginning every time goxdcr re-start. GOXDCR is crashing at statistic manager service due to race condition. I still working on finding solution. -Thanks Ritesh

            People

              wayne Wayne Siu
              wayne Wayne Siu
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty