You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2015/03/24 02:55:52 UTC
[jira] [Commented] (BIGTOP-1772) Split init-hdfs.sh script and let
the individual modules take care of folder creation
[ https://issues.apache.org/jira/browse/BIGTOP-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377089#comment-14377089 ]
jay vyas commented on BIGTOP-1772:
----------------------------------
hi vishnu.
You're right :) Thats why we have init-hcfs.json as the driver for all this.
init-hdfs.sh is just a wrapper we're planning to deplrecate.
You can see the BIGTOP-1200 and BIGTOP-952 jiras for details, and look at cos' completion of BIGTOP-1235 for the full story.
> Split init-hdfs.sh script and let the individual modules take care of folder creation
> -------------------------------------------------------------------------------------
>
> Key: BIGTOP-1772
> URL: https://issues.apache.org/jira/browse/BIGTOP-1772
> Project: Bigtop
> Issue Type: Improvement
> Components: Init scripts
> Affects Versions: 0.8.0
> Reporter: vishnu gajendran
>
> Currently, there is one init-hdfs.sh script which is responsible for creating folders in hdfs for other services like hbase, oozie etc.. This adds depedency between modules (for example, before starting hbase master, we need to ensure that this script is run) which gets further complicated in a scenario where different components run on different node. In order to avoid this, we can let the individual modules take care of creating respective folders in hdfs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)