You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Cameron McKenzie (JIRA)" <ji...@apache.org> on 2014/11/04 01:13:34 UTC

[jira] [Closed] (CURATOR-140) Support the initial data for the node in InterProcessReadWriteLock

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

Cameron McKenzie closed CURATOR-140.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.7.1

> Support the initial data for the node in InterProcessReadWriteLock
> ------------------------------------------------------------------
>
>                 Key: CURATOR-140
>                 URL: https://issues.apache.org/jira/browse/CURATOR-140
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>            Reporter: Azrael
>            Priority: Minor
>             Fix For: 2.7.1
>
>
> Currently, locks(writeLock, readLock) in InterProcessReadWriteLock use the InetAddress for a initial data for the node, It is a little difficult to debug the lock owner as it shows only IP. If the initial data for lock node can be set, participantNodes contains the given information(hostname, id). So, it is easy  to debug participantNodes.
> {code}
> writeLock = InterProcessReadWriteLock.writeLock();
> Collection<String> nodes = writeLock.getParticipantNodes();
> for (String node: nodes) {
>     String nodeData = new String(client.getData().forPath(node));
> }
> {code} 
> {{nodeData}} should be the information which is given in argument.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)