mg-schema-test-database: Provide some timeouts which are better for testing

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.Jackson@eu.citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>

diff --git a/mg-schema-test-database b/mg-schema-test-database
index bf82c75ae87e162370bfc4159d63341b85a9cce1..818cf899b0d1007f64d4f828dc37de786533d886 100755 (executable)
--- 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