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

GOGC is reset to 0 after offline upgrade on the source node

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 5.0.0, 5.1.0
    • 4.6.0, 4.6.1, 4.6.2, 4.6.3, 5.0.0
    • XDCR
    • Untriaged
    • Centos 64-bit
    • Yes

    Description

      Steps:

      • Configure two servers with Couchbase Server 4.1.2
      • Enable unidirectional replication between two nodes
      • Upgrade the source node (rpm -Uv couchbase-server-enterprise-4.6.2-centos7.x86_64.rpm)

      Observed:

      GlobalSettingChangeListener 2017-08-30T13:36:49.422-07:00 [INFO] new Global settings=GoMaxProcs:4, GoGC:0
      GlobalSettingChangeListener 2017-08-30T13:36:49.423-07:00 [INFO] Successfully changed  GOGC setting from(old) 100 to(New) 0
      

       curl -s http://Administrator:password@172.23.96.105:8091/settings/replications | python -mjson.tool
      {
          "checkpointInterval": 1800,
          "docBatchSizeKb": 2048,
          "failureRestartInterval": 10,
          "goGC": 0,
          "goMaxProcs": 4,
          "logLevel": "Info",
          "optimisticReplicationThreshold": 256,
          "sourceNozzlePerNode": 2,
          "statsInterval": 1000,
          "targetNozzlePerNode": 2,
          "workerBatchSize": 500
      }
      

      And thousands GC events afterwards.

      egrep -o 'NumGC":[0-9]+' goxdcr.log 
      NumGC":3093
      NumGC":5696
      NumGC":8315
      

      Attachments

        Issue Links

          Activity

            People

              yu Yu Sui (Inactive)
              pavelpaulau Pavel Paulau (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty