[
https://issues.apache.org/jira/browse/GEODE-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16344275#comment-16344275
]
ASF subversion and git services commented on GEODE-4328:
--------------------------------------------------------
Commit 52ff5ef3e541bcbc4a427a7dc35588ff9b6f3b16 in geode's branch
refs/heads/develop from [~nreich]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=52ff5ef ]
GEODE-4328: Make backup into a task run by a single thread (#1351)
* The BackupLock had to acquire and release the underlying lock and keep
* track of who was supposed to be the true owner of the lock due to the fact
* that the part of backup that acquired the locks was done on a different
* thread than the one that release the locks. Since the backup task now is
* completed in a single thread, we can replace it with a ReentrantLock.
> Make backup a single task
> -------------------------
>
> Key: GEODE-4328
> URL: https://issues.apache.org/jira/browse/GEODE-4328
> Project: Geode
> Issue Type: Sub-task
> Components: persistence
> Reporter: Nick Reich
> Assignee: Nick Reich
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, a backup involves two distributed messages: one that starts the
> process up until a synchronization point and a second that signals to
> complete the backup once synchronization is complete. The current
> implementation results in different threads doing the two halves of the
> process and causes complex logic in locking resources that must be maintained
> over the two threads.
>
> To improve this, the entire backup action can be refactored into a single
> task that gates on CountdownLatches to be released on message receipt.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
