[ https://issues.apache.org/jira/browse/GEODE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Schuchardt closed GEODE-5349. ----------------------------------- > State-flush operation may terminate waiting for current operations, allowing > for cache inconsistency > ---------------------------------------------------------------------------------------------------- > > Key: GEODE-5349 > URL: https://issues.apache.org/jira/browse/GEODE-5349 > Project: Geode > Issue Type: Bug > Components: regions > Reporter: Bruce Schuchardt > Assignee: Bruce Schuchardt > Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > The state-flush operation relies in part on > DistributionAdvisor.waitForCurrentOperations() to stall until in-process > replication efforts have written their messages to communication channels. > This method currently has a self-imposed time limit of > (2*ack-wait-threshold)-1 seconds, which defaults to 29 seconds. If a cache > operation, say a transaction commit, happens to take longer than this the > waitForCurrentOperations() method will terminate early, possibly allowing a > new copy of a region to miss the changes contained in that cache operation. > We should remove the timeout in waitForCurrentOperations and rigorously test > the change. -- This message was sent by Atlassian JIRA (v7.6.3#76005)