Details
-
New Feature
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
6.2.0
-
None
Description
The current system for starting a thor relies on ssh and rsync. We would like to eventually be able to move towards just launching a thorslave on an individual node without needing an ssh connection of any type. To do this though we will need to know the individual slavenumber and port for each slave that is assigned to a cluster. This can be done at configuration time and embedded in the environment xml, and then accessed by a configgen -listall2 call.
Currently the output from a configgen call with "-listall2 -ip localhost -t thor" will yeild:
ThorMasterProcess,mythor,10.20.8.37,20000,/var/lib/HPCCSystems/mythor,
ThorSlaveProcess,mythor,10.20.8.37,,/var/lib/HPCCSystems/mythor,
If the element after the IP could return the slaveport, and if we could possibly insert a column into the record to output the slavenum, that would be extremly helpful.
I could then parse that from configgen directly instead of doing the math for port and slavenumber allocation in our thorslave scripts.
Attachments
Issue Links
- relates to
-
HPCC-15636 envgen - Add support for cloud orchestration
-
- Resolved
-