The default timeouts mean that after starting a test db queue daemon
and a test db allocation attempt, we have to wait two minutes.
Lower timeouts increase the risk that we might lose noncritical races
and allocate resources to the `wrong' tasks. And they reduce the
duration of an outage which will cause a planned allocation attempt to
fail.
I think we don't care about those problems for test instances.
Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
---
mg-schema-test-database | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mg-schema-test-database b/mg-schema-test-database
index bf82c75..818cf89 100755
--- a/mg-schema-test-database
+++ b/mg-schema-test-database
@@ -336,6 +336,8 @@ QueueDaemonHost $ctrlhost
OwnerDaemonPort ${ctrlports%,*}
QueueDaemonPort ${ctrlports#*,}
ExecutiveDbOwningRoleRegexp .*
+QueueDaemonHoldoff 3
+QueueDaemonRetry 5
END
mv -f $tcfg.tmp $tcfg
--
1.7.10.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
