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

[jira] [Commented] (AMBARI-4366) Manage ZooKeeper configs with zoo.cfg

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

Aleksandr Kovalenko commented on AMBARI-4366:
---------------------------------------------

+1 for the patch

> Manage ZooKeeper configs with zoo.cfg
> -------------------------------------
>
>                 Key: AMBARI-4366
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4366
>             Project: Ambari
>          Issue Type: New Feature
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-4366.patch
>
>
> h3. Install Wizard > Customize Services
> Under ZooKeeper tab, there's a new section called "Custom zoo.cfg", just like "Custom core-site.xml" (with the ability to add / override properties).  Also, relevant properties exposed in General/Advanced sections should go into "zoo.cfg".
> h3. Services > ZooKeeper > Config
> Mirror the changes in Install Wizard > Customize Services.
> h3. Add Services Wizard
> Mirror the changes in Install Wizard > Customize Services.
> h3. Add Hosts Wizard > Configurations
> Make sure that the ZooKeeper config group can be selected.
> h3. Misc
> Config changes to zoo.cfg should trigger restart indicator, actual pushing of zoo.cfg file content on the servers, etc.



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