[
https://issues.apache.org/jira/browse/HDFS-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571587#comment-17571587
]
Wei-Chiu Chuang edited comment on HDFS-16645 at 7/26/22 7:38 PM:
-----------------------------------------------------------------
[~smeng] and I encountered a similar problem.
For the context: we started to notice that JN directory can have multiple
inprogress files after enabling multiple standby namenodes in a Hadoop 3.1
based cluster. And it crashed the new SbNN. But we suspect it is an old bug not
really caused by multiple standby NN.
was (Author: jojochuang):
[~smeng] and I encountered a similar problem.
For the context: we started to notice that JN directory can have multiple
inprogress files after enabling multiple standby namenodes in a Hadoop 3.1
based cluster. But we suspect it is an old bug not really caused by multiple
standby NN.
> Multi inProgress segments caused "Invalid log manifest"
> -------------------------------------------------------
>
> Key: HDFS-16645
> URL: https://issues.apache.org/jira/browse/HDFS-16645
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: ZanderXu
> Assignee: ZanderXu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> {code:java}
> java.lang.IllegalStateException: Invalid log manifest (log [1-?
> (in-progress)] overlaps [6-? (in-progress)])[[6-? (in-progress)], [1-?
> (in-progress)]] CommittedTxId: 0
> at
> org.apache.hadoop.hdfs.server.protocol.RemoteEditLogManifest.checkState(RemoteEditLogManifest.java:62)
> at
> org.apache.hadoop.hdfs.server.protocol.RemoteEditLogManifest.<init>(RemoteEditLogManifest.java:46)
> at
> org.apache.hadoop.hdfs.qjournal.server.Journal.getEditLogManifest(Journal.java:740)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
