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

node does not remove completely in upgrade cluster from 1.8.0 to 1.8.1 in windows

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.8.1
    • Fix Version/s: bug-backlog
    • Component/s: ns_server
    • Security Level: Public
    • Labels:
      None
    • Environment:
      windows 2008 R2 64 bit
    • Triage:
      Untriaged

      Description

      Install cocubase server 1.8.0 on 3 nodes 24, 25 and 73
      Create defautl bucket and load 100K items to this bucket
      Do offline upgrade this cluster to couchbase server 1.8.1-927
      Install couchbase server 1.8.1-927 on node 23 with custom install path c:/data-a and custom data path c:/data
      Add node 23 to cluster
      Create 2 more buckets, one is sasl and onther is dedicated port and load 100K items to these buckets
      Load additional 100K items to default bucket.
      Remove node 24 out of cluster. After rebalance done, node 24 was out the cluster but not reeset back to initial setup. Any change in node 24 will see in log of cluster.
      At node 24, the rebalance button was clickable. Click rebalance on node 24 and see rebalance running. I stop rebalance and see data lost in default bucket on the cluster (lost 35 K items over 200 K items)

      1. 10.3.2.23-8091-diag.txt.gz
        1.44 MB
        Thuan Nguyen
      2. 10.3.2.24-8091-diag.txt.gz
        1.14 MB
        Thuan Nguyen
      3. 10.3.2.25-8091-diag.txt.gz
        1.77 MB
        Thuan Nguyen
      4. 10.3.2.73-8091-diag.txt.gz
        1.32 MB
        Thuan Nguyen
      5. log-after-add-back.tgz
        6.00 MB
        Thuan Nguyen
      1. Screen Shot 2012-06-20 at 4.31.41 PM.png
        205 kB
      2. Screen Shot 2012-06-20 at 5.28.15 PM.png
        35 kB
      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        does this only happen when adding a 1.8.0 node back to the cluster ?

        Show
        farshid Farshid Ghods (Inactive) added a comment - does this only happen when adding a 1.8.0 node back to the cluster ?
        Hide
        thuan Thuan Nguyen added a comment -

        All nodes in cluster were offline upgraded to 1.8.1. The removed node is master node of cluster before add a clean install 1.8.1 node to cluster.
        This master node was not clean remove. So I can not add back to cluster.

        Show
        thuan Thuan Nguyen added a comment - All nodes in cluster were offline upgraded to 1.8.1. The removed node is master node of cluster before add a clean install 1.8.1 node to cluster. This master node was not clean remove. So I can not add back to cluster.
        Hide
        peter peter added a comment -

        This is not a regression most likely. We have seen it very infrequently. Alk added logging to gain more insight. We'll try to determine a fix by the 2.0 beta timeframe.

        Show
        peter peter added a comment - This is not a regression most likely. We have seen it very infrequently. Alk added logging to gain more insight. We'll try to determine a fix by the 2.0 beta timeframe.
        Hide
        peter peter added a comment -

        Keeping it open for our upgrade testing.

        Show
        peter peter added a comment - Keeping it open for our upgrade testing.
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        Hehe 1.8.1 is dead.

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - Hehe 1.8.1 is dead.

          People

          • Assignee:
            Unassigned
            Reporter:
            thuan Thuan Nguyen
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes