[
https://issues.apache.org/jira/browse/CASSANDRA-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668039#comment-15668039
]
Ariel Weisberg edited comment on CASSANDRA-12894 at 11/15/16 7:36 PM:
----------------------------------------------------------------------
I think it's a bug in the test. It waits for the victim thread to get into the
WAITING state to indicate is blocked on backpressure which is unreliable
because there are multiple reasons it could be in the waiting state. It could
just wait for the thread to block on the condition we care about (backpressure)
instead of using an unreliable proxy indicator.
The one second spin is also not particularly generous.
What versions do we fix this in?
*edit*
Looks like 3.0, trunk. What is the the cassandra-3.X branch?
was (Author: aweisberg):
I think it's a bug in the test. It waits for the victim thread to get into the
WAITING state to indicate is blocked on backpressure which is unreliable
because there are multiple reasons it could be in the waiting state. It could
just wait for the thread to block on the condition we care about (backpressure)
instead of using an unreliable proxy indicator.
The one second spin is also not particularly generous.
What versions do we fix this in?
> testall failure in
> org.apache.cassandra.hints.HintsBufferPoolTest.testBackpressure-compression
> ----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-12894
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12894
> Project: Cassandra
> Issue Type: Test
> Reporter: Michael Shuler
> Assignee: Ariel Weisberg
> Labels: test-failure
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_testall/720/testReport/org.apache.cassandra.hints/HintsBufferPoolTest/testBackpressure_compression
> {noformat}
> Error Message
> null
> Stacktrace
> junit.framework.AssertionFailedError: null
> at
> org.apache.cassandra.hints.HintsBufferPoolTest.testBackpressure(HintsBufferPoolTest.java:73)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$10.evaluate(BMUnitRunner.java:371)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:241)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:75)
> Standard Output
> ERROR 16:26:27 SLF4J: stderr
> INFO 16:26:27 Configuration location:
> file:/home/automaton/cassandra/test/conf/cassandra.yaml
> INFO 16:26:27 Node configuration:[allocate_tokens_for_keyspace=null;
> authenticator=null; authorizer=null; auto_bootstrap=true; auto_snapshot=true;
> batch_size_fail_threshold_in_kb=50; batch_size_warn_threshold_in_kb=5;
> batchlog_replay_throttle_in_kb=1024; broadcast_address=null;
> broadcast_rpc_address=null; buffer_pool_use_heap_if_exhausted=true;
> cas_contention_timeout_in_ms
> ...[truncated 8324 chars]...
> NA OS native malloc/free
> INFO 16:26:30 Initializing counter cache with capacity of 6 MBs
> INFO 16:26:30 Scheduling counter cache save to every 7200 seconds (going to
> save all keys).
> INFO 16:26:31 Global buffer pool is enabled, when pool is exahusted (max is
> 512 mb) it will allocate on heap
> INFO 16:26:31 Initializing hints_buffer_test.table
> INFO 16:26:31 byteman jar is
> /home/automaton/cassandra/build/lib/jars/byteman-3.0.3.jar
> INFO 16:26:31 Setting org.jboss.byteman.allow.config.update=true
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)