Add how to collect from remote hosts that exceed the default host collect timeout
Closes-bug: 2068506 Change-Id: I8bd8e383391f29d8b5120a46b6bfcc5bd8cb45ce Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com>
This commit is contained in:
parent
297649d3e0
commit
1acc9a534d
@ -75,9 +75,22 @@ Collect Tool Caveats and Usage
|
||||
(keystone_admin)$ collect --all [--timeout | -t] <minutes>
|
||||
|
||||
.. note::
|
||||
|
||||
For large deployments, the default timeout value (20 minutes) may
|
||||
need to be increased by using the ``--timeout`` (``-t``) option.
|
||||
|
||||
The timeout for collecting from the local host, the host that collect
|
||||
is run from, does adopt the global timeout.
|
||||
|
||||
To fix that, run ``collect`` with an extended ``--timeout`` locally on
|
||||
the host that is experiencing the timeout. That way the global timeout
|
||||
applies.
|
||||
|
||||
Optionally, you can modify the default ``COLLECT_HOST_TIMEOUT_DEFAULT``
|
||||
value in the ``/etc/collect/collect_timeouts`` file. That requires
|
||||
``sudo`` command and no processes need to be restarted after the
|
||||
change. All subsequent collects will adopt the new values in that file.
|
||||
|
||||
|
||||
- For subcloud deployments:
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user