[jira] [Updated] (YARN-1641) ZK store should attempt a write periodically to ensure it is still Active

2014-02-11 Thread Karthik Kambatla (JIRA)

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

Karthik Kambatla updated YARN-1641:
---

Attachment: yarn-1641-2.patch

Added thread name. 

> ZK store should attempt a write periodically to ensure it is still Active
> -
>
> Key: YARN-1641
> URL: https://issues.apache.org/jira/browse/YARN-1641
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: resourcemanager
>Affects Versions: 2.3.0
>Reporter: Karthik Kambatla
>Assignee: Karthik Kambatla
> Attachments: yarn-1641-1.patch, yarn-1641-2.patch
>
>
> Fencing in ZK store kicks in when the RM tries to write something to the 
> store. If the RM doesn't write anything to the store, it doesn't get fenced 
> and can continue to assume being the Active. 
> By periodically writing a file (say, every RM_ZK_TIMEOUT_MS seconds), we can 
> ensure it gets fenced.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Updated] (YARN-1641) ZK store should attempt a write periodically to ensure it is still Active

2014-02-10 Thread Karthik Kambatla (JIRA)

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

Karthik Kambatla updated YARN-1641:
---

Summary: ZK store should attempt a write periodically to ensure it is still 
Active  (was: ZK store - periodically create a dummy file to kick in fencing)

> ZK store should attempt a write periodically to ensure it is still Active
> -
>
> Key: YARN-1641
> URL: https://issues.apache.org/jira/browse/YARN-1641
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: resourcemanager
>Affects Versions: 2.3.0
>Reporter: Karthik Kambatla
>Assignee: Karthik Kambatla
> Attachments: yarn-1641-1.patch
>
>
> Fencing in ZK store kicks in when the RM tries to write something to the 
> store. If the RM doesn't write anything to the store, it doesn't get fenced 
> and can continue to assume being the Active. 
> By periodically writing a file (say, every RM_ZK_TIMEOUT_MS seconds), we can 
> ensure it gets fenced.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)