DynamicLoadBalancingPolicy: LatencyAwareHClientPool may throw NoSuchElementException under certain circumstances #650

jsbret opened this Issue Jan 16, 2014 · 1 comment

2 participants


In version 1.1-4, the call to "latencies.remove()" (LatencyAwareHClientPool line 48) may throw a NoSuchElementException if the "resetThread" (See DynamicLoadBalancingPolicy instantiation line 62-74) clear the "latencies" LinkedBlockingDeque just before.

Using the poll() method instead of remove() should fix the issue.

How can i submit a patch ?



Looks like it's been fixed.
Any chance this will be ported into a 1.1 release? Or is support for Cassandra 1.1 essentially deprecated?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment