GitHub user remibergsma opened a pull request:
https://github.com/apache/cloudstack/pull/1467
Lower the time we wait for interfaces to appear after restart
Waiting for interfaces is tricky. They might never appear.. for example
when we have entries in `/etc/cloudstack/ips.json` that haven't been plugged
yet. Waiting this long makes everything horribly slow (every vm, interface,
static route, etc, etc, will hit this wait, for every device). We've seen
CloudStack send an `ip_assoc.json` command for `eth1` public nic only and then
the router goes crazy waiting for all other interfaces that were there before
reboot and aren't there. If only the router would return to the mgt server a
success of `eth1`, it would get the command for `eth2` etc etc. Obviously, a
destroy works much faster because no state services, so no knowledge of
previous devices so no waits :-)
After a stop/start the router has state in `/etc/cloudstack/ips.json` and
every commands waits. Eventually hitting the hardcoded 120 sec timeout.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/remibergsma/cloudstack 47_lower_interface_wait
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1467.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1467
----
commit 3636ad1114a89101ed0a14520572b5f0203d454b
Author: Remi Bergsma <git...@remi.nl>
Date: 2016-02-25T21:48:54Z
lower the time we wait for interfaces to appear
They might never appear.. for example when we have entries in
/etc/cloudstack/ips.json that haven't been plugged yet. Waiting
this long makes everything horribly slow (every vm, interface,
static route, etc, etc, will hit this wait, for every device).
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
