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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.4.0
• Fix Version/s: 0.4.0
• Component/s: general
• Assignee: Roman Shaposhnik
• Reporter: Roman Shaposhnik
• Created: 22/Mar/12 16:44
• Updated: 21/Jun/13 23:55
• Resolved: 28/Mar/12 01:03

Description

The following services require an explicit initialization of the persistent state in the local filesystem:

1. Hadoop NameNode (formatting a namenode via: hdfs namenode -format)
2. 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.):

1. oozie DB (initialized via ooziedb.sh)
2. possible Hive metastore
3. 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.