You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2014/01/09 12:05:55 UTC

[jira] [Updated] (AMBARI-4242) Zookeeper dataDir can not be updated when using Ambari

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

Vitaly Brodetskyi updated AMBARI-4242:
--------------------------------------

    Attachment: AMBARI-4242.patch

> Zookeeper dataDir can not be updated when using Ambari
> ------------------------------------------------------
>
>                 Key: AMBARI-4242
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4242
>             Project: Ambari
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.2.4
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>         Attachments: AMBARI-4242.patch
>
>
> If you install a cluster using Ambari your zookeeper Datadir is locked once the cluster is successfully installed. The option is permenantly greyed out and you cannot update it via the zoo.cfg (Ambari overwrites it)
> You can, however, update it in the zoo.cfg and start zookeeper manually. When you start it through Ambari then it gets overwritten.
> It would be good if you could modify this property via Ambari
> (Maybe for best practice we could maybe add dataLogDir so logging and snapshots will not compete for the same disk I/O)



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