You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Shwetha G S (JIRA)" <ji...@apache.org> on 2015/05/18 09:12:26 UTC

[jira] [Updated] (OOZIE-1923) ZKLocksService locks are not re-entrant like MemoryLocks

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

Shwetha G S updated OOZIE-1923:
-------------------------------
    Fix Version/s:     (was: 4.1.0)
                       (was: trunk)
                   4.2

> ZKLocksService locks are not re-entrant like MemoryLocks
> --------------------------------------------------------
>
>                 Key: OOZIE-1923
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1923
>             Project: Oozie
>          Issue Type: Bug
>          Components: HA
>            Reporter: Purshotam Shah
>            Assignee: Purshotam Shah
>             Fix For: 4.2
>
>         Attachments: OOZIE-1923-V1.patch, OOZIE-1923-V2.patch
>
>
> This is because we are creating InterProcessReadWriteLock instance for every path. 
> We should store InterProcessReadWriteLock and reuse for same path like MemoryLocksService.
> We should also add tests for both ZKLocksService and MemoryLocksService to verify.



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