[CASSANDRA-16186] SEPExecutor does not release blocked threads as it should

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.24, 3.11.10, 4.0-beta4, 4.0
• Component/s: Test/unit
• Epic Link: 40_Quality_Test
• Complexity: Normal

Source Control Link

https://github.com/apache/cassandra/commit/3b970ddbd6c0018ee13b596dddfd838c43afa4d1

Test and Documentation Plan

The patch add some unit tests that check the behavior of the JMXEnabledExecutor and SEPExecutor.

• Assignee: Benjamin Lerer
• Reporter: Benjamin Lerer

Authors

Benjamin Lerer

Reviewers

Andres de la Peña

• Created: 06/Oct/20 09:48
• Updated: 03/Jan/21 16:58
• Resolved: 10/Nov/20 09:56

Description

While adding some tests for the ThreadPoolMetrics, I discovered that the SEPExecutor does not release the blocked threads as it should.

If the number of tasks added to a SEPExecutor exceed the max queue size. The threads adding those task will be block until enough space become available for all the blocked tasks. At this point all the blocked threads will released at once.

Issue Links

• is a child of: CASSANDRA-15582 4.0 quality testing: metrics