[
https://issues.apache.org/jira/browse/CASSANDRA-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050604#comment-14050604
]
Joshua McKenzie commented on CASSANDRA-7390:
--------------------------------------------
bq. It's using a single executor thread and a queue of length one, so if an
operation is already in flight, we will still queue up one more.
Good call - I completely missed the fact that we were providing a workQueue for
the thing to queue up jobs. I'll pull that from the conservative and re-attach.
As for messing with TMD - having dug through the code a bit I agree that
modifying access patterns and synchronization on a component this complex opens
the door to some unintended consequences. Hopefully targeting 3.0 w/this
change should give us plenty of time to bake this in.
> MoveTest fails intermittently
> -----------------------------
>
> Key: CASSANDRA-7390
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7390
> Project: Cassandra
> Issue Type: Bug
> Reporter: Joshua McKenzie
> Assignee: Joshua McKenzie
> Priority: Minor
> Fix For: 3.0
>
> Attachments: 7390_conservative_v1.txt, 7390_conservative_v2.txt,
> 7390_lockpendingcalc.txt
>
>
> Reproduce with:
> for i in `seq 1 50`; do runTest MoveTest >> moveTestFailures.txt;done
> Looks to fail roughly once out of every 5 runs or so
> {code:title=failure}
> [junit] Testcase:
> newTestWriteEndpointsDuringMove(org.apache.cassandra.service.MoveTest):
> FAILED
> [junit] mismatched number of moved token expected:<0> but was:<1>
> [junit] junit.framework.AssertionFailedError: mismatched number of moved
> token expected:<0> but was:<1>
> [junit] at
> org.apache.cassandra.service.MoveTest.newTestWriteEndpointsDuringMove(MoveTest.java:140)
> {code}
> Edit: had this as Windows-only - turns out it's failing on on *nix as well
--
This message was sent by Atlassian JIRA
(v6.2#6252)
