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

Increasing the default timeouts on ns_server to avoid rebalance failures due to ep-engine stats timeout issues in large cluster or clusters where some nodes are actively using swap


    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.8.1-release-candidate
    • Fix Version/s: 1.8.1
    • Component/s: ns_server
    • Security Level: Public
    • Labels:
    • Environment:
      Windows small/large cluster
      Linux small/large cluster

      Bucket 1, default
      vbuckets 1024
      RAM 18.7G
      Nodes 4 ( 2 form the base-cluster)
      Items Setup for 20M items


      Related issues:-

      We have multiple bugs related to the timeouts we are hitting on ns_server :-
      1) When in swap
      2) On windows even on a small cluster.

      This bug is to recommend increasing the default timeouts.

      We used the following timeouts on most of the params, its not all in one solution, but hopefully would cover basic secnarios.
      ns_memcached_outer, 60000
      ns_memcached_open_checkpoint, 60000
      ns_memcached_outer_heavy, 60000
      ns_memcached_outer_very_heavy, 120000
      ns_memcached_connected, 10000
      ebucketmigrator_connect, 60000

      Summary, some error messages and fixes that worked:-
      1) Rebalance exited with reason



      Fix : adjust timeout value - 120sec - ns_memcached_outer_very_heavy
      2) Rebalance exited with reason {exited,

      Fix: Adjust timeout value - 120 sec - ns_memcached_outer_heavy

      3) Rebalance exited with reason {exited,




      Fix : Adjust timeout to 120sec
      4) Rebalance exited with reason {{change_filter_failed,

      Fix : Adjust timeout values -
      ebucketmigrator_connect 120 secs
      ns_memcached_connected 1 sec

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



          • Assignee:
            alkondratenko Aleksey Kondratenko (Inactive)
            karan Karan Kumar (Inactive)
          • Votes:
            0 Vote for this issue
            1 Start watching this issue


            • Created:

              Gerrit Reviews

              There are no open Gerrit changes