You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Francesco Nigro (Jira)" <ji...@apache.org> on 2021/06/20 16:03:00 UTC

[jira] [Updated] (CURATOR-598) InterProcessSemaphoreV2::getData to check against data changes on the semaphore

     [ https://issues.apache.org/jira/browse/CURATOR-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Nigro updated CURATOR-598:
------------------------------------
    Description: 
InterProcessSemaphoreV2 allows holders to set data on the acquired lease: exposing an Optional<byte[]> getData would allow an observer to check against mutex state change despite not being the lock owner (assuming owner has used setData prior a mutex acquisition).
This can be used to weakly enforce order of mutex acquisition or just check owner's identity and/or presence (assuming owner setData prior a mutex acquisition).

  was:
InterProcessSemaphoreV2 allows holders to set data on the acquired lease: exposing an Optional<byte[]> getData would allow an observer to check against mutex state change despite not being the lock owner (assuming owner has used setData prior a mutex acquisition).
This can be used to enforce the order of mutex acquisition or just check owner's identity and/or presence (assuming owner setData prior a mutex acquisition).


> InterProcessSemaphoreV2::getData to check against data changes on the semaphore
> -------------------------------------------------------------------------------
>
>                 Key: CURATOR-598
>                 URL: https://issues.apache.org/jira/browse/CURATOR-598
>             Project: Apache Curator
>          Issue Type: New Feature
>          Components: Recipes
>    Affects Versions: 5.1.0
>            Reporter: Francesco Nigro
>            Priority: Major
>
> InterProcessSemaphoreV2 allows holders to set data on the acquired lease: exposing an Optional<byte[]> getData would allow an observer to check against mutex state change despite not being the lock owner (assuming owner has used setData prior a mutex acquisition).
> This can be used to weakly enforce order of mutex acquisition or just check owner's identity and/or presence (assuming owner setData prior a mutex acquisition).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)