Revision f30d0610 man/hail.rst
b/man/hail.rst | ||
---|---|---|
27 | 27 |
If the input file name is ``-`` (a single minus sign), then the request |
28 | 28 |
data will be read from *stdin*. |
29 | 29 |
|
30 |
Apart from input data, hail collects data over the network from all |
|
31 |
MonDs with the --mond option. Currently it uses only data produced by |
|
32 |
the CPUload collector. |
|
33 |
|
|
30 | 34 |
ALGORITHM |
31 | 35 |
~~~~~~~~~ |
32 | 36 |
|
... | ... | |
75 | 79 |
in the JSON request itself. This is mostly used for debugging. The |
76 | 80 |
format of the file is described in the man page **htools**\(1). |
77 | 81 |
|
82 |
\--mond |
|
83 |
If given the program will query all MonDs to fetch data from the |
|
84 |
supported data collectors over the network. |
|
85 |
|
|
86 |
\--mond-data *datafile* |
|
87 |
The name of the file holding the data provided by MonD, to override |
|
88 |
quering MonDs over the network. This is mostly used for debugging. The |
|
89 |
file must be in JSON format and present an array of JSON objects , |
|
90 |
one for every node, with two members. The first member named ``node`` |
|
91 |
is the name of the node and the second member named ``reports`` is an |
|
92 |
array of report objects. The report objects must be in the same format |
|
93 |
as produced by the monitoring agent. |
|
94 |
|
|
95 |
\--ignore-dynu |
|
96 |
If given, all dynamic utilisation information will be ignored by |
|
97 |
assuming it to be 0. This option will take precedence over any data |
|
98 |
passed by the MonDs with the ``--mond`` and the ``--mond-data`` |
|
99 |
option. |
|
100 |
|
|
78 | 101 |
\--simulate *description* |
79 | 102 |
Backend specification: similar to the **-t** option, this allows |
80 | 103 |
overriding the cluster data with a simulated cluster. For details |
Also available in: Unified diff