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

XDCR: Go-1.6 tracking bug: Replication lag time increased in build 4.5.0-2428 (compared to 4.5.0-2359)

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Incomplete
    • 4.5.0
    • None
    • XDCR
    • Build: 4.5.0-2428
      Test: 90th percentile replication lag time (xdcr_5x5_unidir_500M_dgm_2b.test)

    Description

      4.5.0-2428 was built with go 1.6.
      90%tile Replication lag time (in ms)

      4.5.0-2151 (1.5) 4.5.0-2359 (1.5) 4.5.0-2428 (1.6) 4.5.0-2488 (1.6) 4.5.0-2570 (1.5) 4.5.0-2585 (1.5)
      3 4 8 9 5 3

      Attachments

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

        Activity

          Ascending order - Click to sort in descending order
          View 6 older comments
          qi Qi Zhu (Inactive) added a comment -

          OK. Latest result in show fast with build 2151 shows lag time to be 3ms.

          Is this build(2151) with Go 1.5?
          Does this mean this bug only happens with Go 1.6?

          Thanks,
          Qi

          qi Qi Zhu (Inactive) added a comment - OK. Latest result in show fast with build 2151 shows lag time to be 3ms. Is this build(2151) with Go 1.5? Does this mean this bug only happens with Go 1.6? Thanks, Qi
          wayne Wayne Siu added a comment -

          The current assumption about the regression was introduced by go 1.6.

          wayne Wayne Siu added a comment - The current assumption about the regression was introduced by go 1.6.
          jliang John Liang added a comment -

          For 1.6, go-xdcr has to put in additional synchronization primitive to avoid race. That is needed regardless go-1.5 or go-1.6

          jliang John Liang added a comment - For 1.6, go-xdcr has to put in additional synchronization primitive to avoid race. That is needed regardless go-1.5 or go-1.6
          jliang John Liang added a comment -

          This is not a regression for watson. But it is a tracking bug when moving to go-1.6 in 4.5.1

          jliang John Liang added a comment - This is not a regression for watson. But it is a tracking bug when moving to go-1.6 in 4.5.1
          wayne Wayne Siu added a comment -

          Closing this ticket for now.
          When we move to a newer version of GO, we'll get the new data.
          Should regression happens (which we have tests to cover this case in weekly crank), we'll open a new ticket.

          wayne Wayne Siu added a comment - Closing this ticket for now. When we move to a newer version of GO, we'll get the new data. Should regression happens (which we have tests to cover this case in weekly crank), we'll open a new ticket.

          People

            yu Yu Sui (Inactive)
            wayne Wayne Siu
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty