hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12812) Ozone: dozone: initialize scm and ksm directory on cluster startup
Date Thu, 26 Apr 2018 21:57:07 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16455378#comment-16455378

Hudson commented on HDFS-12812:

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14070 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14070/])
HDFS-12812. Ozone: dozone: initialize scm and ksm directory on cluster (omalley: rev 10e1e2c2f5964a3f5c3cfb18be0757b1e9e381ec)
* (edit) dev-support/compose/ozone/docker-compose.yaml

> Ozone: dozone: initialize scm and ksm 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
>            Assignee: Elek, Marton
>            Priority: Major
>             Fix For: HDFS-7240
>         Attachments: HADOOP-12812-HDFS-7240.001.patch, HDFS-12812-HDFS-7240.002.patch
> 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.
> UPDATE: the patch also contains envrionment variable to initialize the ksm.
> 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message