hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDDS-40) Separating packaging of Ozone/HDDS from the main Hadoop
Date Thu, 10 May 2018 13:41:00 GMT
Elek, Marton created HDDS-40:

             Summary: Separating packaging of Ozone/HDDS from the main Hadoop
                 Key: HDDS-40
                 URL: https://issues.apache.org/jira/browse/HDDS-40
             Project: Hadoop Distributed Data Store
          Issue Type: Improvement
            Reporter: Elek, Marton
            Assignee: Elek, Marton

According to the community vote, Ozone/Hdds release cycle should be independent from the Hadoop
release cycle.

To make it possible we need a separated ozone package.

*The current state:*

We have just one output tar/directory under hadoop-dist (hadoop-3.2.0). It includes all the
hdfs/yarn/mapreduce/hdds binaries and libraries. (Jar files are put in separated directory).

The hdds components and hdfs compobebts all could be started from the bin. 

*Proposed version*

Create a sepearated hadoop-dist/ozone-2.1.0 which contains only the hdfs AND hdds components.
Both the hdfs namenode and hdds datanode/scm/ksm could be started from the ozone-2.1.0 package.

Hdds packages would be removed from the original hadoop-3.2.0 directory.

This is a relatively small change. On further JIRAs we need to :

 * Create a shaded datanode plugin which could be used with any existing hadoop cluster
 * Use standalone ObjectStore/Ozone server instead of the Namenode+Datanod plugin.
 * Add test cases for both the ozone-only and the mixed clusters (ozone + hdfs)

This message was sent by Atlassian JIRA

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

View raw message