[
https://issues.apache.org/jira/browse/HDFS-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299228#comment-16299228
]
Anu Engineer commented on HDFS-12812:
-------------------------------------
KSM is not running after I apply this patch.
{noformat}
STARTUP_MSG: build = https://git-wip-us.apache.org/repos/asf/hadoop.git -r
d3acb451a0c9e89cc44985233066c35d291ec4e8; compiled by 'aengineer' on
2017-12-20T22:52Z
STARTUP_MSG: java = 1.8.0_151
************************************************************/
2017-12-20 23:11:55 INFO KeySpaceManager:51 - registered UNIX signal handlers
for [TERM, HUP, INT]
2017-12-20 23:11:56 WARN NativeCodeLoader:60 - Unable to load native-hadoop
library for your platform... using builtin-java classes where applicable
2017-12-20 23:11:56 ERROR KeySpaceManager:268 - Failed to start the
KeyspaceManager.
org.apache.hadoop.ozone.ksm.exceptions.KSMException: KSM not initialized.
at
org.apache.hadoop.ozone.ksm.KeySpaceManager.<init>(KeySpaceManager.java:134)
at
org.apache.hadoop.ozone.ksm.KeySpaceManager.createKSM(KeySpaceManager.java:307)
at
org.apache.hadoop.ozone.ksm.KeySpaceManager.main(KeySpaceManager.java:262)
2017-12-20 23:11:56 INFO ExitUtil:210 - Exiting with status 1:
org.apache.hadoop.ozone.ksm.exceptions.KSMException: KSM not initialized.
2017-12-20 23:11:56 INFO KeySpaceManager:51 - SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down KeySpaceManager at 5dfe646f02f1/172.18.0.3
************************************************************/
{noformat}
I cleared all docker images on my system, pulled new images and this is the
output from from running {{docker logs ozone_ksm_1}}
> 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
> Assignee: Elek, Marton
> 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.
> 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
