[CASSANDRA-9328] WriteTimeoutException thrown when LWT concurrency > 1, despite the query duration taking MUCH less than cas_contention_timeout_in_ms

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Won't Fix
• Component/s: Feature/Lightweight Transactions, Legacy/Coordination
• Labels: LWT
• Severity: Normal
• Assignee: Unassigned
• Reporter: Aaron Whiteside
• Created: 07/May/15 22:10
• Updated: 30/Jan/24 15:04
• Resolved: 02/Feb/16 14:54

Description

WriteTimeoutException thrown when LWT concurrency > 1, despite the query duration taking MUCH less than cas_contention_timeout_in_ms.

Unit test attached, run against a 3 node cluster running 2.1.5.

If you reduce the threadCount to 1, you never see a WriteTimeoutException. If the WTE is due to not being able to communicate with other nodes, why does the concurrency >1 cause inter-node communication to fail?

Issue Links

• depends upon: CASSANDRA-6246 EPaxos
• is related to: CASSANDRA-15350 Separate exceptions for CAS write timeout exceptions caused by contention and unknown result