Fixed com.netflix.astyanax.connectionpool.exceptions.PoolTimeoutException

[sbtourist]

Previously, a com.netflix.astyanax.connectionpool.exceptions.PoolTimeoutException was occurring when running a test with a number of concurrent threads higher than 2. This was due to MaxBlockedThreadsPerHost not set into com.netflix.jmeter.connections.a6x.AstyanaxConnection.

[sbtourist]

The problem is, if that configuration isn't set, and you have more threads than configured hosts, exceeding threads will be timed-out by the Astyanax client pool with PoolTimeoutException, making your tests basically fail (try that if you want to be sure, but should be fairly intuitive too).

What you suggest may be correct, but the other way around: that is, set MaxConnsPerHost and MaxBlockedThreadsPerHost equal one to the other by default so that the case above (pretty common with small clusters imho) can work, and eventually override externally.

[sbtourist]

Any further comments? Did you have the chance to actually try it?

[epikhinm]

I think this should be another different option with new interface field. Connections not equal threads queue per connection. This option can overflow when i use many connections with many threads.