You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/03/18 22:07:00 UTC
[jira] [Commented] (HDDS-4997) SCM Fails to start after downgrade
due to No enum constant
org.apache.hadoop.hdds.protocol.DatanodeDetails.Port.Name.REPLICATION
[ https://issues.apache.org/jira/browse/HDDS-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304492#comment-17304492 ]
Ethan Rose commented on HDDS-4997:
----------------------------------
cc [~adoroszlai] [~elek]
> SCM Fails to start after downgrade due to No enum constant org.apache.hadoop.hdds.protocol.DatanodeDetails.Port.Name.REPLICATION
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDDS-4997
> URL: https://issues.apache.org/jira/browse/HDDS-4997
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ethan Rose
> Assignee: Ethan Rose
> Priority: Major
> Attachments: scm.log
>
>
> When running downgrade tests for HDDS-4181, SCM failed to start when downgraded from 1.1.0 pre-finalized to 1.0.0. Log file is attached. It looks like HDDS-4496 introduced the incompatibility, and HDDS-4731 and HDDS-4851 (both applied when the test was run) provided some fixes, but not enough to support downgrades to 1.0.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org