hpcc-systems/HPCC-Platform — pull request #6544 by Michael-Gardner (2014-10-16 20:33:10+00:00)
Title: HPCC-12325 Making hpcc-run.sh run in parallel by default

The number of threads passed to cluster_script.py will be equal to the number of machines with hpcc components in the environment. When using the -c flag, we now branch and only target the specific nodes that the component is located on, as well as giving an error message and print_usage if the user inputs a component name that isn't found using configgen. The user may still choose to limit the number of threads by using the -n flag. If the -S flag (for sequential use of hpcc-run.sh) is used, it overrides any usage of the -n flag. Added documentation in print_usage() to convey this change in behavior. This is still not entirely asynchronous, as we must give precedence to the node containing Dali, as it is a prerequisite for most of the other components within the system.

Signed-off-by: Michael Jon Gardner