Description of problem: 15:40:27,367 INFO [org.rhq.server.metrics.StorageSession] (Cassandra Java Driver worker-12) /17.176.208.118 is up 15:40:27,367 INFO [org.rhq.server.metrics.StorageSession] (Cassandra Java Driver worker-12) Changing request throughput from 30000.0 request/sec to 40000.0 requests/sec 15:40:27,367 INFO [org.rhq.enterprise.server.storage.StorageClusterMonitor] (Cassandra Java Driver worker-12) Storage cluster is up 15:40:27,368 INFO [org.rhq.enterprise.server.storage.StorageClusterMonitor] (Cassandra Java Driver worker-12) Storage node at 17.176.208.118 is up 15:40:28,096 INFO [org.rhq.server.metrics.StorageSession] (Cassandra Java Driver worker-13) /17.176.208.118 is up 15:40:28,096 INFO [org.rhq.server.metrics.StorageSession] (Cassandra Java Driver worker-13) Changing request throughput from 40000.0 request/sec to 50000.0 requests/sec 15:40:28,096 INFO [org.rhq.enterprise.server.storage.StorageClusterMonitor] (Cassandra Java Driver worker-13) Storage node at 17.176.208.118 is up Seems like a race condition... The rate should be 30000 not go up to 50000 Version-Release number of selected component (if applicable): 4.12 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I am marking this as a blocker for bug 1100309 which is the BZ against which the throttling work is being tracked.
Fixed in master: commit 57c72fd8254998281c157852d0f3bf3e363c09a6 Author: Michael Burman <miburman> Date: Tue Oct 7 12:36:50 2014 +0300 [BZ 1098243] [BZ 1149342] When encountering a timeout on StorageSession, recreate RateLimiter with higher warmup time.