You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Elek, Marton (JIRA)" <ji...@apache.org> on 2017/11/14 17:00:00 UTC
[jira] [Created] (HDFS-12812) Ozone: dozone: initialize scm
directory on cluster startup
Elek, Marton created HDFS-12812:
-----------------------------------
Summary: Ozone: dozone: initialize scm directory on cluster startup
Key: HDFS-12812
URL: https://issues.apache.org/jira/browse/HDFS-12812
Project: Hadoop HDFS
Issue Type: Sub-task
Components: ozone
Affects Versions: HDFS-7240
Reporter: Elek, Marton
HDFS-12739 fixed the scm, but after the patch it couldn't be started without a separated `hdfs scm -init` any more. Unfortunatelly it breaks the docker-compose functionality.
This is handled int the starter script of the base runner docker image for namenode. I also fixed this in the runner docker image (https://github.com/elek/hadoop/commit/b347eb4bfca37d84dbcdd8c4bf353219d876a9b7) will upload the improved patch to the HADOOP-14898.
In this patch I just add a new environment variable to init the scm if the version file doesn't exist.
To test:
Do a full build and go to the dev-support/compose/ozone:
```
docker-compose pull
docker-compose up -d
```
Note: the pull is important as the new docker image -- which could handle the new environment variable -- should be used
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org