GitHub user christian-esken opened a pull request:
https://github.com/apache/cassandra/pull/95
Expire messages by a single Thread
When queue expiration is done, one single Thread is elected to do the
work. Previously, all Threads would go in and do the same work,
producing high lock contention. The Thread reading from the Queue could
even be starved by not be able to acquire the read lock. CASSANDRA-13265
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/christian-esken/cassandra 13265b-3.0
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cassandra/pull/95.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #95
----
commit 448d7a9c1430d9f23bd819895fc618bb227ca833
Author: Christian Esken <christian.es...@trivago.com>
Date: 2017-03-01T14:56:36Z
Expire messages by a single Thread
When queue expiration is done, one single Thread is elected to do the
work. Previously, all Threads would go in and do the same work,
producing high lock contention. The Thread reading from the Queue could
even be starved by not be able to acquire the read lock. CASSANDRA-13265
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
