accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1310) Fate's DistributedReadWriteLock shouldn't poll
Date Thu, 23 May 2013 14:53:20 GMT

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

John Vines updated ACCUMULO-1310:
---------------------------------

    Issue Type: Sub-task  (was: Improvement)
        Parent: ACCUMULO-715
    
> Fate's DistributedReadWriteLock shouldn't poll
> ----------------------------------------------
>
>                 Key: ACCUMULO-1310
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1310
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: fate
>            Reporter: John Vines
>            Assignee: Keith Turner
>
> Currently DistributedReadWriteLock.tryLock polls every 100ms to obtain a lock. There
are fancier mechanisms, like using Watchers to do this. There's also probably a curator recipe
for this as an alternative.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message