You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@twill.apache.org by "Terence Yim (JIRA)" <ji...@apache.org> on 2014/10/21 19:12:34 UTC

[jira] [Commented] (TWILL-104) Enable users to specify a different node than root of Zookeeper for Twill application data

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

Terence Yim commented on TWILL-104:
-----------------------------------

Currently Twill uses ZooKeeper chroot ability to have namespacing ([http://zookeeper.apache.org/doc/r3.4.6/zookeeperProgrammers.html#ch_zkSessions]). For example if you specify the zkConnectStr as:

{{my.zk.host:2181/twill}}

Then Twill will only operates on nodes under the "/twill" folder.

Is that something you are looking for or something more than that?

Terence

> Enable users to specify a different node than root of Zookeeper for Twill application data
> ------------------------------------------------------------------------------------------
>
>                 Key: TWILL-104
>                 URL: https://issues.apache.org/jira/browse/TWILL-104
>             Project: Apache Twill
>          Issue Type: Improvement
>          Components: yarn
>    Affects Versions: 0.3.0-incubating, 0.4.0-incubating, 0.5.0-incubating
>            Reporter: Mike Walch
>
> In YarnTwillRunnerService.watchLiveApps(), all child nodes of the Zookeeper root are considered Twill applications and are watched for changes.  On a cluster, other non-twill applications could be storing data in the same zookeeper.  It would be better if "/twill" was used for the root or if users could specify another root path in Zookeeper for Twill data.  Watching the Zookeeper nodes of non-twill applications could be causing the delay seen in TWILL-103.



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