Tell the remote support to TCP_RESET the connection to the given remote peer.
Tell the remote support to TCP_RESET the connection to the given remote peer. It works regardless of whether the recipient was initiator or responder.
is the symbolic name of the node which is to be affected
is the symbolic name of the other node to which connectivity shall be impeded
Switch the Netty pipeline of the remote support into blackhole mode for sending and/or receiving: it will just drop all messages right before submitting them to the Socket or right after receiving them from the Socket.
Switch the Netty pipeline of the remote support into blackhole mode for sending and/or receiving: it will just drop all messages right before submitting them to the Socket or right after receiving them from the Socket.
To use this feature you must activate the TestConductorTranport
by specifying testTransport(on = true) in your MultiNodeConfig.
is the symbolic name of the node which is to be affected
is the symbolic name of the other node to which connectivity shall be impeded
can be either Direction.Send, Direction.Receive or Direction.Both
Tell the remote support to shutdown the connection to the given remote peer.
Tell the remote support to shutdown the connection to the given remote peer. It works regardless of whether the recipient was initiator or responder.
is the symbolic name of the node which is to be affected
is the symbolic name of the other node to which connectivity shall be impeded
Obtain the list of remote host names currently registered.
Switch the Netty pipeline of the remote support into pass through mode for sending and/or receiving.
Switch the Netty pipeline of the remote support into pass through mode for sending and/or receiving.
To use this feature you must activate the TestConductorTranport
by specifying testTransport(on = true) in your MultiNodeConfig.
is the symbolic name of the node which is to be affected
is the symbolic name of the other node to which connectivity shall be impeded
can be either Direction.Send, Direction.Receive or Direction.Both
Remove a remote host from the list, so that the remaining nodes may still pass subsequent barriers.
Remove a remote host from the list, so that the remaining nodes may still pass subsequent barriers. This must be done before the client connection breaks down in order to affect an “orderly” removal (i.e. without failing present and future barriers).
is the symbolic name of the node which is to be removed
Tell the remote node to shut itself down using System.
Tell the remote node to shut itself down using System.exit with the given exitValue. The node will also be removed, so that the remaining nodes may still pass subsequent barriers.
is the symbolic name of the node which is to be affected
is the return code which shall be given to System.exit
Obtain the port to which the controller’s socket is actually bound.
Obtain the port to which the controller’s socket is actually bound. This
will deviate from the configuration in akka.testconductor.port in case
that was given as zero.
Start the akka.remote.testconductor.Controller, which in turn will
bind to a TCP port as specified in the akka.testconductor.port config
property, where 0 denotes automatic allocation.
Start the akka.remote.testconductor.Controller, which in turn will
bind to a TCP port as specified in the akka.testconductor.port config
property, where 0 denotes automatic allocation. Since the latter is
actually preferred, a Future[Int] is returned which will be completed
with the port number actually chosen, so that this can then be communicated
to the players for their proper start-up.
This method also invokes akka.remote.testconductor.Player.startClient, since it is expected that the conductor participates in barriers for overall coordination. The returned Future will only be completed once the client’s start-up finishes, which in fact waits for all other players to connect.
gives the number of participants which shall connect before any of their startClient() operations complete.
Make the remoting pipeline on the node throttle data sent to or received from the given remote peer.
Make the remoting pipeline on the node throttle data sent to or received
from the given remote peer. Throttling works by delaying packet submission
within the netty pipeline until the packet would have been completely sent
according to the given rate, the previous packet completion and the current
packet length. In case of large packets they are split up if the calculated
send pause would exceed akka.testconductor.packet-split-threshold
(roughly). All of this uses the system’s HashedWheelTimer, which is not
terribly precise and will execute tasks later than they are schedule (even
on average), but that is countered by using the actual execution time for
determining how much to send, leading to the correct output rate, but with
increased latency.
To use this feature you must activate the TestConductorTranport
by specifying testTransport(on = true) in your MultiNodeConfig.
is the symbolic name of the node which is to be affected
is the symbolic name of the other node to which connectivity shall be throttled
can be either Direction.Send, Direction.Receive or Direction.Both
is the maximum data rate in MBit
The conductor is the one orchestrating the test: it governs the akka.remote.testconductor.Controller’s port to which all akka.remote.testconductor.Players connect, it issues commands to their akka.remote.testconductor.NetworkFailureInjector and provides support for barriers using the akka.remote.testconductor.BarrierCoordinator. All of this is bundled inside the akka.remote.testconductor.TestConductorExt extension.