| || |
Scripts running after run stops, requires generator reboot
We've had 4 instances in the past several months where our internal instrumentation picked up a "rogue thread" still running long after the scenario had completed.
Took rebooting the generator to stop the transaction.
Anyone had any instances where a generator keeps running a script after the run has stopped and the generator status is "idle"?
happen with one generator or many?
Happens intermittently across several generators.
A few notes: generators are virtuals on the same physical box, have occasionally seen CPU jumps over 80% on these boxes.
"generators are virtuals on the same physical box, have occasionally seen CPU jumps over 80% on these boxes."
Really buys you little from both a process and a total load perspective. It just makes all of the load generators more subject to cross VM influences as they all try to get access to the same resources under load.
Use at least one physical generator as control|reference sample from both an environment and a sampling perspective. No issues on the physical generator but appear on the virtual ones, then that takes you one direction in diagnosing the issue. Appears on all load generators, then that takes you another.