[travis-ci] dtolabs/rundeck#288 (development - 25c448b : Greg Schueler): The build passed.
[travis-ci] Change view : https://github.com/dtolabs/rundeck/compare/be7953333cba…25c448bf74fe
[travis-ci] Build details : http://travis-ci.org/dtolabs/rundeck/builds/8002486
[travis-ci] dtolabs/rundeck#289 (development - 66ed465 : Greg Schueler): The build passed.
[travis-ci] Change view : https://github.com/dtolabs/rundeck/compare/25c448bf74fe…66ed465df0f7
[travis-ci] Build details : http://travis-ci.org/dtolabs/rundeck/builds/8002522
does rundeck spawns 1 jsch thread (or process) per host it has to run 1 job on ?
in general: each exec/script step will use one Jsch connection to a node.
yeah and does that mean 1 thread per connection or 1 process or else ?
There are multiple threads involved, e.g. to read from the input, and to monitor the connection thread. if you use Sudo and the sudo-responder, there are additional threads
[travis-ci] dtolabs/rundeck#290 (development - 28fbf64 : Greg Schueler): The build passed.
[travis-ci] Change view : https://github.com/dtolabs/rundeck/compare/66ed465df0f7…28fbf64e6358
[travis-ci] Build details : http://travis-ci.org/dtolabs/rundeck/builds/8026120
gschueler: you had a pretty nice write up wrt threading
i can clean it up for better general consumption if that helps
Alex-SF: I’m hoping next week I can give the HA vagrant config a test drive
<– guy from the call last week
great. looking forward to hear