Details
-
Bug
-
Resolution: Won't Fix
-
Minor
-
None
-
7.1.0
-
7.1.0-2549
-
Untriaged
-
Centos 64-bit
-
1
-
No
Description
Scenario -
Offline upgrade from 6.5.2 to 7.1.0
Test Steps -
1. Create cluster as follows -
Node | Services | CPU_utilization | Mem_total | Mem_free | Swap_mem_used | Active / Replica | Version |
172.23.121.243 | cbas | 0.501253132832 | 3.91 GiB | 3.06 GiB | 0.0 Byte / 3.50 GiB | 0 / 0 | 6.5.2-6634-enterprise |
172.23.105.31 | index, kv, n1ql | 0.501253132832 | 3.91 GiB | 3.39 GiB | 66.75 MiB / 3.50 GiB | 0 / 0 | 6.5.2-6634-enterprise |
172.23.105.244 | index, kv, n1ql | 1.25944584383 | 3.91 GiB | 3.41 GiB | 39.00 MiB / 3.50 GiB | 0 / 0 | 6.5.2-6634-enterprise |
172.23.105.245 | cbas | 2.01511335013 | 3.91 GiB | 3.13 GiB | 78.25 MiB / 3.50 GiB | 0 / 0 | 6.5.2-6634-enterprise |
172.23.121.244 | cbas | 0.503778337531 | 3.91 GiB | 2.99 GiB | 0.0 Byte / 3.50 GiB | 0 / 0 | 6.5.2-6634-enterprise |
2. Create a bucket and load 10K docs.
3. Create dataverses and datasets on cbas.
4. Wait for ingestion to finish.
5. Failover a node, upgrade it using rpm -u and then add it back to cluster.
6. Do this for all the nodes of cluster.
7. Once all the nodes are upgraded, rebalance once again to activate analytics.
8. The Local link for one of the dataverse apart from Default is disconnected.
Other observations -
I tried 2 scenarios for the above test.
1. 2 Dataverses (including Deafult) and 4 datasets in each dataverse.
2. 4 Dataverses (including Deafult) and 2 datasets in each dataverse.
Above infra is created Pre-upgrade.
Now in 1st case, the Local link is always disconnected for the non-Default dataverse.
For 2nd case, all the Local links are connected.
Note- No error is thrown if we explicitly connect the disconnected link and continue the test further.