[
https://issues.apache.org/jira/browse/OOZIE-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Purshotam Shah updated OOZIE-1922:
----------------------------------
Description:
ReentrantLock can be acquired multiple times in same thread. For multiple
acquire call, ReentrantLock hold count is incremented by one.
So if we acquire lock multiple time from same thread, all will be successful
and hold count is increased for every call.
But if we release lock, MemoryLocksService ignore the count and deletes the
lock. Even if it's held by some command.
Simple step can reproduce it.
{code}
service.getWriteLock("test", 5000); //writeHoldCount = 1
MemoryLockToken lock = (MemoryLockToken)service.getWriteLock("test",
5000); //writeHoldCount = 2
lock.release(); //writeHoldCount = 1
lock = (MemoryLockToken)service.getWriteLock("test", 5000);
//writeHoldCount = 1, it should be 2.
{code}
> MemoryLocksService fails if lock is acquired multiple times in same thread
> and released
> ---------------------------------------------------------------------------------------
>
> Key: OOZIE-1922
> URL: https://issues.apache.org/jira/browse/OOZIE-1922
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
>
> ReentrantLock can be acquired multiple times in same thread. For multiple
> acquire call, ReentrantLock hold count is incremented by one.
> So if we acquire lock multiple time from same thread, all will be successful
> and hold count is increased for every call.
> But if we release lock, MemoryLocksService ignore the count and deletes the
> lock. Even if it's held by some command.
> Simple step can reproduce it.
> {code}
> service.getWriteLock("test", 5000); //writeHoldCount = 1
> MemoryLockToken lock = (MemoryLockToken)service.getWriteLock("test",
> 5000); //writeHoldCount = 2
> lock.release(); //writeHoldCount = 1
> lock = (MemoryLockToken)service.getWriteLock("test", 5000);
> //writeHoldCount = 1, it should be 2.
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
