hpcc-systems/HPCC-Platform — Issue #1633: Docs - configmgr multi-node assumptions
Author: rengolin
Created: 2012-02-21 12:30:45+00:00
State: open

I was following the configmgr doc (HPCC Configuration Manager) to create a dual-node cluster. I managed to create one, however, not in my first attempt and with some additional info from Richard.

The issues I had:

* The assumption that all nodes must have exactly the same hpccsystems package installed. Some clustering software (Sun's GRID Engine, Rocks) have different packages for masters, slaves, configuration nodes, health-check nodes etc. so this is not a valid assumption. Please, make it explicit on the beginning of the docs: "have all nodes installed but not started", for instance.
* It's possible that this is in another doc, so at least, there should be a link/reference to it. (and back)
* It's not clear that the master node is not master to either Roxie or Thor. The alert pop-ups on the automatic configuration do stop you from creating a bogus config, and they tell you (a bit) why the numbers are required, but they don't tell you the underlying reason, ie, Thor's master is actually, the slave node. (#1495 ?)
* I only realised that when I started the cluster and saw the topology. Then I had to go back to the file, add node001 to Thor's topology, copying files to /etc and restarting the service. However, in EclWatch, Thor's topology is still master/slave on node002.

Other issues seem to be covered by currently open issues on configmgr, so I won't mention them.

Would be good (if we'll keep configmgr) to have a more verbose automatic generation of the configuration. The advanced view is for experts, and it's good the way it is, but the simplified / automatic is for noobs (like me), so a few explanations here and there, and a more verbose warning on mistakes is much welcomed.