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

Analytics storage path not recognized

    XMLWordPrintable

Details

    • Untriaged
    • 1
    • Yes

    Description

      Setup analytics with 32 stage paths which are not recognized when adding the server to the cluster. I had to add each of the 3 disk individually.

      Attachments

        For Gerrit Dashboard: MB-48720
        # Subject Branch Project Status CR V

        Activity

          ritam.sharma Ritam Sharma added a comment -

          Daniel Owen - This is approved for 7.0.2.

          ritam.sharma Ritam Sharma added a comment - Daniel Owen - This is approved for 7.0.2.
          owend Daniel Owen added a comment -

          Thanks Ritam Sharma

          owend Daniel Owen added a comment - Thanks Ritam Sharma

          Build couchbase-server-7.0.2-6703 contains ns_server commit 801bd51 with commit message:
          MB-48720: show full list of Analytics storage path during cluster/node..

          build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.2-6703 contains ns_server commit 801bd51 with commit message: MB-48720 : show full list of Analytics storage path during cluster/node..

          Build couchbase-server-7.1.0-1457 contains ns_server commit 801bd51 with commit message:
          MB-48720: show full list of Analytics storage path during cluster/node..

          build-team Couchbase Build Team added a comment - Build couchbase-server-7.1.0-1457 contains ns_server commit 801bd51 with commit message: MB-48720 : show full list of Analytics storage path during cluster/node..
          umang.agrawal Umang added a comment -

          Verified on build 7.0.2-6703.

          Steps - 

          1. Create a 1 node cluster with KV, N1ql and analytics service.
          2. Now on another new node (we will call it New1) set the analytics path as follows -

          [root@node2-cb660-centos7 analytics]# /opt/couchbase/bin/couchbase-cli node-init -c http://127.0.0.1:8091 -u Administrator -p password --node-init-analytics-path /analytics/disk1 --node-init-analytics-path /analytics/disk2 --node-init-analytics-path /analytics/disk3 --node-init-analytics-path /analytics/disk4 --node-init-analytics-path /analytics/disk5 --node-init-analytics-path /analytics/disk6 --node-init-analytics-path /analytics/disk7 --node-init-analytics-path /analytics/disk8 --node-init-analytics-path /analytics/disk9 --node-init-analytics-path /analytics/disk10 --node-init-analytics-path /analytics/disk11 --node-init-analytics-path /analytics/disk12 --node-init-analytics-path /analytics/disk13 --node-init-analytics-path /analytics/disk14 --node-init-analytics-path /analytics/disk15 --node-init-analytics-path /analytics/disk16 --node-init-analytics-path /analytics/disk17 --node-init-analytics-path /analytics/disk18 --node-init-analytics-path /analytics/disk19 --node-init-analytics-path /analytics/disk20 --node-init-analytics-path /analytics/disk21 --node-init-analytics-path /analytics/disk22 --node-init-analytics-path /analytics/disk23 --node-init-analytics-path /analytics/disk24 --node-init-analytics-path /analytics/disk25 --node-init-analytics-path /analytics/disk26 --node-init-analytics-path /analytics/disk27 --node-init-analytics-path /analytics/disk28 --node-init-analytics-path /analytics/disk29 --node-init-analytics-path /analytics/disk30 --node-init-analytics-path /analytics/disk31 --node-init-analytics-path /analytics/disk32
          

          3. On node New1, go to join cluster setup.

          4. All the 32 paths set in step 2 are shows in setup form.

          5. Add node New1 to the cluster and rebalance.

          6. Verify analytics is working fine.

          umang.agrawal Umang added a comment - Verified on build 7.0.2-6703. Steps -  Create a 1 node cluster with KV, N1ql and analytics service. Now on another new node (we will call it New1) set the analytics path as follows - [root @node2 -cb660-centos7 analytics]# /opt/couchbase/bin/couchbase-cli node-init -c http: //127.0.0.1:8091 -u Administrator -p password --node-init-analytics-path /analytics/disk1 --node-init-analytics-path /analytics/disk2 --node-init-analytics-path /analytics/disk3 --node-init-analytics-path /analytics/disk4 --node-init-analytics-path /analytics/disk5 --node-init-analytics-path /analytics/disk6 --node-init-analytics-path /analytics/disk7 --node-init-analytics-path /analytics/disk8 --node-init-analytics-path /analytics/disk9 --node-init-analytics-path /analytics/disk10 --node-init-analytics-path /analytics/disk11 --node-init-analytics-path /analytics/disk12 --node-init-analytics-path /analytics/disk13 --node-init-analytics-path /analytics/disk14 --node-init-analytics-path /analytics/disk15 --node-init-analytics-path /analytics/disk16 --node-init-analytics-path /analytics/disk17 --node-init-analytics-path /analytics/disk18 --node-init-analytics-path /analytics/disk19 --node-init-analytics-path /analytics/disk20 --node-init-analytics-path /analytics/disk21 --node-init-analytics-path /analytics/disk22 --node-init-analytics-path /analytics/disk23 --node-init-analytics-path /analytics/disk24 --node-init-analytics-path /analytics/disk25 --node-init-analytics-path /analytics/disk26 --node-init-analytics-path /analytics/disk27 --node-init-analytics-path /analytics/disk28 --node-init-analytics-path /analytics/disk29 --node-init-analytics-path /analytics/disk30 --node-init-analytics-path /analytics/disk31 --node-init-analytics-path /analytics/disk32 3. On node New1, go to join cluster setup. 4. All the 32 paths set in step 2 are shows in setup form. 5. Add node New1 to the cluster and rebalance. 6. Verify analytics is working fine.

          People

            umang.agrawal Umang
            ron.graham Ron Graham
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty