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

It takes more than 5 minutes to stop an empty Couchbase Server node

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Blocker
    • 4.5.1
    • 4.5.1
    • couchbase-bucket
    • None
    • Untriaged
    • Centos 64-bit
    • Yes

    Description

      Build: 4.5.1-2829.

      Steps:
      1. Create a cluster with 2 nodes.
      2. Create an empty non-default bucket with SASL auth.

      {
          "authType": "sasl", 
          "bucketType": "membase", 
          "evictionPolicy": "valueOnly", 
          "flushEnabled": 1, 
          "name": "bucket-1", 
          "ramQuotaMB": 51200, 
          "replicaIndex": 0, 
          "replicaNumber": 1, 
          "saslPassword": "password"
      }
      

      3. Restart one of the servers.

      # time service couchbase-server restart
      Restarting couchbase-server (via systemctl):               [  OK  ]
       
      real	5m0.471s
      user	0m0.036s
      sys	0m0.057s
      

      It's not really OK. In fact, the stop task just timed out:

      # systemctl show couchbase-server.service | grep Timeout
      TimeoutStartUSec=5min
      TimeoutStopUSec=5min
      

      Because of that the "start" part of the "restart" task had no affect:

      # service couchbase-server status
      couchbase-server is not running
      

      Attachments

        1. ares01_4.5.1-2838.zip
          16.08 MB
        2. ares01.zip
          13.18 MB
        3. ares02_4.5.1-2838.zip
          13.07 MB
        4. ares02.zip
          9.43 MB

        Issue Links

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

          Activity

            People

              drigby Dave Rigby (Inactive)
              pavelpaulau Pavel Paulau (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty