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 2018/09/13 09:59:00 UTC

[jira] [Created] (HDDS-446) Provide shaded artifact to start ozone service as a datanode plugin

Elek, Marton created HDDS-446:
---------------------------------

             Summary: Provide shaded artifact to start ozone service as a datanode plugin
                 Key: HDDS-446
                 URL: https://issues.apache.org/jira/browse/HDDS-446
             Project: Hadoop Distributed Data Store
          Issue Type: Improvement
            Reporter: Elek, Marton
            Assignee: Elek, Marton
             Fix For: 0.2.1


Ozone datanode service could be started in two different way:
 # as a standalone process
 # as a datanode plugin

We tested the second scenarion by compiling both ozone + hadoop trunk together and created a combined artifact. But we have no more full hadoop distribution in the ozone release package any more. And we had no answer how it could be started with an existing hadoop release.

We need a well defined way to add the datanode-service to the classpath of the hadoop datanode.

I propose here to create a lightweight shaded artifact (and here the shading only combines all the classes together without package name refactoring) to make it easier to extend an existing hadoop installation.

In this patch I add the shade plugin execution to the ozone objectstore-service and the shaded file will be copied to the distribution.

A new docker-compose based execution environment (ozone-hdfs) demonstrates/tests how it could work.

Tested with hadoop 3.1.0 and datanode service could be started without any problem



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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