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

didn't get error in logs after stopping server in second time: Could not auto-failover node ('IP'). Cluster was too small, you need at least 2 other nodes.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 3.0
    • 2.1.0, 2.2.0
    • ns_server
    • Security Level: Public
    • Untriaged

    Description

      steps:
      1. set autofailove 30 secs
      2. set email alerts settings
      3. 2 nodes in cluster (112, 113)
      4. stop node 113
      observation :
      get error in logs as expected
      Could not auto-failover node ('ns_1@10.3.121.113'). Cluster was too small, you need at least 2 other nodes.
      auto_failover004 ns_1@10.3.121.112 13:47:37 - Mon Apr 15, 2013
      Node 'ns_1@10.3.121.112' saw that node 'ns_1@10.3.121.113' went down. Details: [

      {nodedown_reason, connection_closed}] ns_node_disco005 ns_1@10.3.121.112 13:47:07 - Mon Apr 15, 2013
      5. restart 113 and rebalance out from cluster

      Here I played with three nodes in clusters, but do not think that these steps are important

      6. 1 node 112 in cluster, set again autofailove 30 secs and email alerts settings( test mail)
      7. rebalance in 113 node and the stop it

      result:

      get only message that node 113 went down

      Node 'ns_1@10.3.121.112' saw that node 'ns_1@10.3.121.113' went down. Details: [{nodedown_reason, connection_closed}

      ]

      I believe that the user should again get the message "Could not auto-failover node ('IP'). Cluster was too small, you need at least 2 other nodes."

      Attachments

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

        Activity

          People

            iryna iryna
            andreibaranouski Andrei Baranouski
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty