Changes
Page history
cumin: limiting batch size in order to avoid weird connection issues
authored
Sep 16, 2024
by
lelutin
Hide whitespace changes
Inline
Side-by-side
howto/cumin.md
View page @
17b9ae71
...
@@ -160,6 +160,18 @@ an alias in the following way:
...
@@ -160,6 +160,18 @@ an alias in the following way:
Or you can instead use the automatic ssh tunnel trick above, making sure to
Or you can instead use the automatic ssh tunnel trick above, making sure to
change the path to cumin in the bash function.
change the path to cumin in the bash function.
## Avoiding spurious connection errors by limiting batch size
If your ssh configuration makes all hosts use the same
`ProxyJump`
, you might be
seeing some strange and fluctuating percentage of hosts will error out on
connection. This is because you are hitting your ssh proxy's max connections per
IP. This could be caused by the server's
`MaxSessions`
which defaults to 10.
In order to avoid weird issues, you should limit your batch size to 10 or lower,
e.g.:
cumin -b 10 'F:os.distro.codename=bookworm' 'apt update'
## Example commands
## Example commands
This will run the
`uptime`
command on all hosts:
This will run the
`uptime`
command on all hosts:
...
...
...
...