After Rack Expansion Mammoth Upgrade Only Shows Upgrade Actions Done on the Original Rack
Last updated on MAY 18, 2018
Applies to:Big Data Appliance Integrated Software - Version 4.8.0 and later
The symptoms are that after an expansion to nodes in a new rack, Mammoth upgrade only shows upgrade actions done on the original rack(s).
Note: The example here is of a single rack cluster comprised of 15 nodes that was expanded to include a 6 node starter rack. The end result is a cluster comprised of 2 racks, rack 1 with 15 nodes and rack 2 with 6. However the issue applies to any cluster expansion involving more than one rack.
The sequence of events leading to the state is:
1. A cluster is expanded to include an additional rack. The expanded cluster is fully healthy and functional.
"# dcli -C" correctly accesses all cluster nodes on all racks.
2. The expanded cluster is then upgraded via Mammoth.
3. During the upgrade, Step 1 shows that Mammoth actions are only taken on the nodes in the original rack, rack 1 in the example here. In the example case, Mammoth upgrade actions are only taken on the first 15 nodes in rack 1. No upgrade steps are take place on the nodes in rack 2.
For example, Mammoth upgrade output is like this: