[
https://issues.apache.org/jira/browse/CURATOR-592?focusedWorklogId=610869&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-610869
]
ASF GitHub Bot logged work on CURATOR-592:
------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jun/21 19:36
Start Date: 14/Jun/21 19:36
Worklog Time Spent: 10m
Work Description: MGelbana-Incorta commented on pull request #384:
URL: https://github.com/apache/curator/pull/384#issuecomment-860940282
Creating a completely new class is a great idea!
I'll close this PR for now. Thanks a lot @eolivelli.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 610869)
Time Spent: 1h 10m (was: 1h)
> Provide a callback that is fired after the InterProcessMutex creates its
> ephemeral node
> ---------------------------------------------------------------------------------------
>
> Key: CURATOR-592
> URL: https://issues.apache.org/jira/browse/CURATOR-592
> Project: Apache Curator
> Issue Type: Improvement
> Components: Recipes
> Affects Versions: 5.1.0
> Reporter: Mohamed Mohsen
> Priority: Major
> Labels: Concurrency
> Fix For: TBD
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {{InterProcessMutex}} performs two significant steps to
> [acquire|https://curator.apache.org/apidocs/org/apache/curator/framework/recipes/locks/InterProcessMutex.html#acquire()]
> its lock:
> # Creates an ephemeral sequential node. This practically means that it took
> a position in the lock queue (i.e. based on its sequence value).
> # Blocks until the lock is acquired.
> This improvement is about providing a callback that notifies the caller that
> the lock order is reserved.
> The use for this, at least for us, is that we needed to differentiate between
> the two phases for higher concurrency because we can do other actions after
> knowing that the {{InterProcessMutex}} order is known. Especially since the
> lock acquisition can take too long, depending on the situation of course.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
