[
https://issues.apache.org/jira/browse/GEODE-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664351#comment-16664351
]
ASF subversion and git services commented on GEODE-5922:
--------------------------------------------------------
Commit 3ed37a754d789bb52cf190db23088e819955fd58 in geode's branch
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3ed37a7 ]
GEODE-5922 SerialGatewaySenderQueue concurrency is poorly implemented
Replaced simple synchronization with a fair write-lock. The use of
sync to enforce serial queueing wasn't fair and caused inconsistent
latency. I observed one thread that was blocked trying to get the
sync for over 30 seconds while other subsequent threads were able to
get the sync and queue their events.
This closes #2705
> SerialGatewaySenderQueue concurrency is poorly implemented
> ----------------------------------------------------------
>
> Key: GEODE-5922
> URL: https://issues.apache.org/jira/browse/GEODE-5922
> Project: Geode
> Issue Type: Improvement
> Components: wan
> Reporter: Bruce Schuchardt
> Assignee: Bruce Schuchardt
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This class uses synchronization on the queue to limit access to one put at a
> time. Synchronization isn't a fair locking mechanism so threads can be
> blocked trying to add events to the queue while other more recent events get
> the lock and insert their events. This causes inconsistent latency which
> I've observed being as long as 30 seconds, causing client connections to be
> shut down by the ClientHealthMonitor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
