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/01/13 10:05:00 UTC
[jira] [Updated] (HDDS-2881) Legacy (isolated) ozonefs couldn't
work in secure environments
[ https://issues.apache.org/jira/browse/HDDS-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marton Elek updated HDDS-2881:
------------------------------
Priority: Critical (was: Major)
> Legacy (isolated) ozonefs couldn't work in secure environments
> --------------------------------------------------------------
>
> Key: HDDS-2881
> URL: https://issues.apache.org/jira/browse/HDDS-2881
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Critical
>
> The unsecure ozonefs is tested together with different version of Hadoop (2.7, 3.1, 3.2). The "legacy" (isolated) ozonefs package makes it possible to use it together with older Hadoop versions.
> But the ozonesecure-mr (testing ozonefs with mapreduce in secure Ozone environment) is executed only with Hadoop 3.2 (which uses the "current" (shared) ozonefs instead of the "legacy" (isolated))
> It turned on that the "legacy" ozonefs couldn't work in secure environment which means Ozone can be used only together with Hadoop 3.2 if the Hadoop/Ozone environment is secure
--
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