hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1914) Ozonescript example docker-compose cluster can't be started
Date Wed, 14 Aug 2019 06:43:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1914?focusedWorklogId=294520&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-294520
]

ASF GitHub Bot logged work on HDDS-1914:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Aug/19 06:42
            Start Date: 14/Aug/19 06:42
    Worklog Time Spent: 10m 
      Work Description: anuengineer commented on pull request #1232: HDDS-1914. Ozonescript
example docker-compose cluster can't be started
URL: https://github.com/apache/hadoop/pull/1232
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 294520)
    Time Spent: 1h  (was: 50m)

> Ozonescript example docker-compose cluster can't be started
> -----------------------------------------------------------
>
>                 Key: HDDS-1914
>                 URL: https://issues.apache.org/jira/browse/HDDS-1914
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> the compose/ozonescripts cluster provides an example environment to test the start-ozone.sh
and stop-ozone.sh scripts.
> It starts containers with sshd daemon but witout starting the ozone which makes it possible
to start those scripts.
> Unfortunately the docker files are broken since:
>  * we switched from debian to centos with the base image
>  * we started to use /etc/hadoop instead of /opt/hadoop/etc/hadoop for configuring the
hadoop (workers file should be copied there)
>  * we started to use jdk11 to execute ozone (instead of java8)
> The configuration files should be updated according to these changes. 
> # How to test this patch?
> (1) Do a full build and try to start the ./compose/ozonescripts cluster (check the related
README file in the directory):
> ```
> docker-compose up -d
> ```
> (2) start the ozone processes with ./start.sh (from compose/ozonescripts)
> (3) wait and check if om/scm webui are working and you have 1 healthy datanode



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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


Mime
View raw message