42766b28f1
The failing tests showed big variations in startup times, i.e. JVM1 not started/bound when other JVMs tries to connect to the test conductor. The reconnect logic was in place but it was bound to 10 client-reconnects (10 seconds). It's better to let it by default reconnect until the connect-timeout (20 seconds) is elapsed.
65 lines
2.3 KiB
Text
65 lines
2.3 KiB
Text
#############################################
|
||
# Akka Remote Testing Reference Config File #
|
||
#############################################
|
||
|
||
# This is the reference config file that contains all the default settings.
|
||
# Make your edits/overrides in your application.conf.
|
||
|
||
akka {
|
||
testconductor {
|
||
|
||
# Timeout for joining a barrier: this is the maximum time any participants
|
||
# waits for everybody else to join a named barrier.
|
||
barrier-timeout = 30s
|
||
|
||
# Timeout for interrogation of TestConductor’s Controller actor
|
||
query-timeout = 5s
|
||
|
||
# Threshold for packet size in time unit above which the failure injector will
|
||
# split the packet and deliver in smaller portions; do not give value smaller
|
||
# than HashedWheelTimer resolution (would not make sense)
|
||
packet-split-threshold = 100ms
|
||
|
||
# amount of time for the ClientFSM to wait for the connection to the conductor
|
||
# to be successful
|
||
connect-timeout = 20s
|
||
|
||
# Number of connect attempts to be made to the conductor controller
|
||
client-reconnects = 30
|
||
|
||
# minimum time interval which is to be inserted between reconnect attempts
|
||
reconnect-backoff = 1s
|
||
|
||
netty {
|
||
# (I&O) Used to configure the number of I/O worker threads on server sockets
|
||
server-socket-worker-pool {
|
||
# Min number of threads to cap factor-based number to
|
||
pool-size-min = 1
|
||
|
||
# The pool size factor is used to determine thread pool size
|
||
# using the following formula: ceil(available processors * factor).
|
||
# Resulting size is then bounded by the pool-size-min and
|
||
# pool-size-max values.
|
||
pool-size-factor = 1.0
|
||
|
||
# Max number of threads to cap factor-based number to
|
||
pool-size-max = 2
|
||
}
|
||
|
||
# (I&O) Used to configure the number of I/O worker threads on client sockets
|
||
client-socket-worker-pool {
|
||
# Min number of threads to cap factor-based number to
|
||
pool-size-min = 1
|
||
|
||
# The pool size factor is used to determine thread pool size
|
||
# using the following formula: ceil(available processors * factor).
|
||
# Resulting size is then bounded by the pool-size-min and
|
||
# pool-size-max values.
|
||
pool-size-factor = 1.0
|
||
|
||
# Max number of threads to cap factor-based number to
|
||
pool-size-max = 2
|
||
}
|
||
}
|
||
}
|
||
}
|