You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org> on 2012/03/27 01:18:28 UTC

[jira] [Updated] (BIGTOP-479) init.d scripts should provide an option for initializing persistent state of the services that require it

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

Roman Shaposhnik updated BIGTOP-479:
------------------------------------

    Attachment: BIGTOP-479.patch.txt
    
> init.d scripts should provide an option for initializing persistent state of the services that require it
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-479
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-479
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-479.patch.txt
>
>
> The following services require an explicit initialization of the persistent state in the local filesystem:
>    # Hadoop NameNode (formatting a namenode via: hdfs namenode -format)
>    # ZooKeeper (formatting a local storage area via: zookeeper-server-initialize)
> and the following ones require an initialization of the RDBMS database (which can reside on a local filesystem
> via Derby or be hosted on a remote server such as Postgress, MySQL, Oracle, etc.):
>    # oozie DB (initialized via ooziedb.sh)
>    # possible Hive metastore
>    # possibly Sqoop metastore
> In order to free the user from an explicit knowledge of what command to run under which account it is desirable
> to have an init.d scripts for the above components support and extra command called 'init'.
> Please let me know what do you all think.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira