[ 
https://issues.apache.org/jira/browse/OOZIE-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063968#comment-14063968
 ] 

Rohini Palaniswamy commented on OOZIE-1906:
-------------------------------------------

Puru pointed out that Curator does manage that threadpool and shuts it down. 
Based on what is done here - 
https://git-wip-us.apache.org/repos/asf?p=curator.git;a=blob;f=curator-client/src/main/java/org/apache/curator/utils/CloseableExecutorService.java
 , better to keep the threadpool separate. 

So just fixing the 3rd comment about not exposing the getZKUtils() should be 
enough.

> Service to periodically remove ZK lock
> --------------------------------------
>
>                 Key: OOZIE-1906
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1906
>             Project: Oozie
>          Issue Type: Bug
>          Components: HA
>            Reporter: Purshotam Shah
>            Assignee: Purshotam Shah
>         Attachments: OOZIE-1906-V1.patch
>
>
> We might have a case where lock are held-up and it never released bcz of 
> exception. Service should remove those locks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to