Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
5.6.0
-
None
-
None
Description
Curator has several lock recipes(LeaderLatch, InterProcessMutex and etc.), but it has no simple intuitive method to guard modification under lock path. I am certain that CuratorFramework.transaction is capable of this, but I still want a simple way to archive this.
I implemented one before in rust, but it might be relative hard to it to cooperate well with existing `CreateBuilder`, 'SetDataBuilder` and `DeleteBuilder`.
It need time to explore, post it here for memories.
Attachments
Issue Links
- is related to
-
CURATOR-604 Double locking issue while using InterProcessMutex lock code
- Open