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

linux Upgrade fails on clusters from 181 to 2.0 or 2.0 to 2.0.1 ( node referenced using hostnames)

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0.1
    • Component/s: installer, tools
    • Security Level: Public
    • Labels:
      None
    • Environment:
      181-942 to 2.0-1956

      Description

      Centos 5.7

      • Update 181 nodes w/ hostnames
      • create 181 3 node cluster, 2 buckets ( default and sasl)
      • Load 100k items on both the buckets.

      Take a backup of the data.

      Do an offline upgrade on master node
      rpm -U

      Do an offline upgrade on non-master node
      rpm -U

      No data/buckets after upgrade

      Seeing this error on upgrade
      [root@grape-008 jenkins]# rpm -U couchbase-server-community_x86_64_2.0.0-1956-rel.rpm
      Stopping couchbase-server ...
      Stopping couchbase-server
      Upgrading couchbase-server ...
      /opt/couchbase/bin/install/cbupgrade -c /opt/couchbase/var/lib/couchbase/config -a yes
      Automatic mode: running without interactive questions or confirmations.
      Upgrading your Couchbase Server to 2.0.0-1956-rel.
      The upgrade process might take awhile.
      Analysing...
      Previous config.dat file is /opt/couchbase/var/lib/couchbase/config/config.dat
      Target node: ns_1@127.0.0.1
      Done: previous node configuration is empty.
      Starting couchbase-server[ OK ]

      You have successfully installed Couchbase Server.
      Please browse to http://grape-008:8091/ to configure your server.
      Please refer to http://couchbase.com for additional resources.

      The upgrade is unable to pickup older node w/ hostname and wrongly identifies it w/ ip address inplace of hostname here.
      Resulting in this being treated as an install instead of upgrade

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

        Activity

        Hide
        steve Steve Yen added a comment -

        bug-scrub - assigning to steve to see if we have a possible smooth 2.0 -> 2.0.1 upgrade pathway.

        Show
        steve Steve Yen added a comment - bug-scrub - assigning to steve to see if we have a possible smooth 2.0 -> 2.0.1 upgrade pathway.
        Hide
        steve Steve Yen added a comment - - edited

        The proposed pathway to handle 2.0 to 2.0.1 upgrade is to...

        – leverage the preinst hooks in rpm and deb packaging systems (assuming they work), and save a copy of any couchbase-server startup scripts.

        – then, the 2.0.1 installer would check whether the "-name" parameter exists in the couchbase-server.save file to compute the node-name; and also save the node-name into an ip file, if it exists.

        – also, 2.0.1's couchbase-server script would be enhanced to source that ip file, if it exists / non-empty.

        Bounced it off of alk and it's not unbearably unreasonable.

        This proposal does not require any more changes to 2.0.0, but would probably require a fair amount of trial and error during 2.0.1.

        Show
        steve Steve Yen added a comment - - edited The proposed pathway to handle 2.0 to 2.0.1 upgrade is to... – leverage the preinst hooks in rpm and deb packaging systems (assuming they work), and save a copy of any couchbase-server startup scripts. – then, the 2.0.1 installer would check whether the "-name" parameter exists in the couchbase-server.save file to compute the node-name; and also save the node-name into an ip file, if it exists. – also, 2.0.1's couchbase-server script would be enhanced to source that ip file, if it exists / non-empty. Bounced it off of alk and it's not unbearably unreasonable. This proposal does not require any more changes to 2.0.0, but would probably require a fair amount of trial and error during 2.0.1.
        Hide
        bcui Bin Cui added a comment -

        In CB-708, we proposed a way to specify hostname in var/lib/couchbase/ip_start, and installer will automatically take care of the hostname as node reference during upgrade.

        We need to modify the current documents to reflect this change for 2.0.1 release.

        For 1.8.x and/or 2.0 customers, you need to specify hostname under <root>/var/lib/couchbase/ip_start before upgrade.

        Show
        bcui Bin Cui added a comment - In CB-708, we proposed a way to specify hostname in var/lib/couchbase/ip_start, and installer will automatically take care of the hostname as node reference during upgrade. We need to modify the current documents to reflect this change for 2.0.1 release. For 1.8.x and/or 2.0 customers, you need to specify hostname under <root>/var/lib/couchbase/ip_start before upgrade.
        Hide
        dipti Dipti Borkar added a comment -

        Per bug-scrub: This needs to be fixed for 2.0.1 in the next 2 weeks.

        Show
        dipti Dipti Borkar added a comment - Per bug-scrub: This needs to be fixed for 2.0.1 in the next 2 weeks.
        Hide
        mccouch MC Brown (Inactive) added a comment -

        I've added notes to the upgrade section on the requirement of the ip_start file, and added an entry to the release notes in prep for the 2.0.1 release with the required info.

        Show
        mccouch MC Brown (Inactive) added a comment - I've added notes to the upgrade section on the requirement of the ip_start file, and added an entry to the release notes in prep for the 2.0.1 release with the required info.

          People

          • Assignee:
            mccouch MC Brown (Inactive)
            Reporter:
            ketaki Ketaki Gangal
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes