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

Upgrade from 4.1 - 4.5.0-2592 - Missing indexes

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Test Blocker
    • Resolution: Fixed
    • 4.5.0
    • 4.5.0
    • forestdb
    • None
    • 2592

    Description

      1. Install 4.1 on 4 nodes and create a cluster - 2 data + 1 index + 1 query
      2. Install travel-sample, verify all indexes are build
      3. Now upgrade each node by using rpm -U to build 2592 (do not stop the server in advance, rpm -U will stop and upgrade)
      4. Login and navigate to Indexes node on UI and there are no indexes any more

      Attachments

        Issue Links

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

          Activity

            I see the same behavior with a 3 node cluster..each having kv,index and query.
            Able to repro with beer-sample.
            Built 3 secondary indexes before upgrade.
            After upgrade I just see 1 index.

            Prerna.Manaktala Prerna Manaktala (Inactive) added a comment - I see the same behavior with a 3 node cluster..each having kv,index and query. Able to repro with beer-sample. Built 3 secondary indexes before upgrade. After upgrade I just see 1 index.
            jung-sang Jung-Sang Ahn (Inactive) added a comment - Just uploaded a fix: http://review.couchbase.org/#/c/64380/

            Sundar - Please use the cluster from yesterday to test the fix before hand off to Prerna a toy build i.e. verify it first.

            tai.tran Tai Tran (Inactive) added a comment - Sundar - Please use the cluster from yesterday to test the fix before hand off to Prerna a toy build i.e. verify it first.

            As the fix resolves the critical functional bug in versioning a commit header, I reviewed and merged for the watson build. But, we will first verify this issue before assigning it back to the QE.

            chiyoung Chiyoung Seo (Inactive) added a comment - As the fix resolves the critical functional bug in versioning a commit header, I reviewed and merged for the watson build. But, we will first verify this issue before assigning it back to the QE.

            I am now verifying it on Tai's cluster.

            sundar Sundar Sridharan (Inactive) added a comment - I am now verifying it on Tai's cluster.

            Works fine with 4.5.0-2593 that carries the fix.

            abhinav Abhinav Dangeti added a comment - Works fine with 4.5.0-2593 that carries the fix.

            Prerna Manaktala Assigning this ticket to you, as I was told that you're verifying this build as well. I verified this to work with build 4.5.0-2593.

            abhinav Abhinav Dangeti added a comment - Prerna Manaktala Assigning this ticket to you, as I was told that you're verifying this build as well. I verified this to work with build 4.5.0-2593.

            Verified that all indexes show up after upgrade to latest build: 4.5.0-2593

            Prerna.Manaktala Prerna Manaktala (Inactive) added a comment - Verified that all indexes show up after upgrade to latest build: 4.5.0-2593

            People

              Prerna.Manaktala Prerna Manaktala (Inactive)
              ritam.sharma Ritam Sharma
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty