[ 
https://issues.apache.org/jira/browse/GEODE-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665707#comment-16665707
 ] 

ASF subversion and git services commented on GEODE-5925:
--------------------------------------------------------

Commit 898a649f5f834ab7406f1486838da94ae468e2e6 in geode's branch 
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=898a649 ]

GEODE-5925 Server shutdown delays election of new primary bucket owners

Addressing nitpick with variable names in old test code


> Server shutdown delays election of new primary bucket owners
> ------------------------------------------------------------
>
>                 Key: GEODE-5925
>                 URL: https://issues.apache.org/jira/browse/GEODE-5925
>             Project: Geode
>          Issue Type: Improvement
>          Components: regions
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> The distributed lock service is configured to avoid releasing locks while the 
> cache is closing.  If the cache that is closing has any primary bucket locks 
> this can delay cache operations on those buckets until the cache is 
> completely closed and the DistributedSystem is disconnected.
> I've seen this take over 30 seconds, causing client connections to be timed 
> out on the server-side and clients failing over from one server to another 
> only to be blocked by the same issue in those servers.
> Another thing I observed at the same time is that AcceptorImpl is sending 
> profile updates for all partitioned regions.  Those profile updates take as 
> long as 2 seconds apiece to process.  This also delays election of new 
> primary bucket owners and it's unnecessary since 
> DestroyPartitionRegion messages are later sent that remove the profiles in 
> other servers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to