You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Marton Elek (Jira)" <ji...@apache.org> on 2020/06/25 10:34:00 UTC
[jira] [Resolved] (HDDS-3858) Remove support to start Ozone and
HDFS datanodes in the same JVM
[ https://issues.apache.org/jira/browse/HDDS-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marton Elek resolved HDDS-3858.
-------------------------------
Fix Version/s: 0.6.0
Resolution: Fixed
> Remove support to start Ozone and HDFS datanodes in the same JVM
> ----------------------------------------------------------------
>
> Key: HDDS-3858
> URL: https://issues.apache.org/jira/browse/HDDS-3858
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.6.0
>
>
> With a few thousands issues ago Ozone was integral part of Hadoop/HDFS project. At that time there were two options to start datanode:
> 1. Start in a separated JVM
> 2. Start in the same JVM with the HDFS
> Today only 1 is the standard way, this is tested and working. 2nd is not working any more but still documented.
> I propose to drop the support of this use case as I can't see any benefit to support it anymore:
> 1. I think 100% of the users will use Ozone as a separated process not as a HDFS Datanode plugin
> 2. Fixing the classpath issues is significant effort as the classpath of HDFS and Ozone are diverged.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org