[
https://issues.apache.org/jira/browse/HDFS-14726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919944#comment-16919944
]
Chen Liang commented on HDFS-14726:
-----------------------------------
[~jhung] I just checked the tests, TestJournalNodeRespectsBindHostKeys and
TestNameNodeMetadataConsistency passed in my local run, and
TestDirectoryScanner is a known flaky test. I will commit this immediately.
As for HDFS-10519, yes, I will change its fix-version. I do also have it on my
list to change the fix-version of all the SBN read Jiras, just haven't got the
bandwidth to work on it. Will do it soon.
> Fix JN incompatibility issue in branch-2 due to backport of HDFS-10519
> ----------------------------------------------------------------------
>
> Key: HDFS-14726
> URL: https://issues.apache.org/jira/browse/HDFS-14726
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
> Affects Versions: 2.10.0
> Reporter: Chen Liang
> Assignee: Chen Liang
> Priority: Blocker
> Labels: release-blocker
> Attachments: HDFS-14726-branch-2.001.patch,
> HDFS-14726-branch-2.002.patch, HDFS-14726-branch-2.003.patch
>
>
> HDFS-10519 has been backported to branch-2. However HDFS-10519 introduced an
> incompatibility issue between NN and JN due to the new protobuf field
> {{committedTxnId}} in {{HdfsServer.proto}}. This field was introduced as a
> required field so if JN and NN are not on same version, it will run into
> missing field exception. Although currently we can get around by making sure
> JN always gets upgraded properly before NN, we can potentially fix this
> incompatibility by changing the field to optional.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
