[
https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huhaiyang updated HDFS-15391:
-----------------------------
Description:
In the cluster version 3.2.0 production environment，
We found that due to edit log corruption, Standby NameNode could not properly
load the Ediltog log, result in abnormal exit of the service and failure to
restart
The specific scenario is that Flink writes to HDFS, and in the case of an
exception to the write file, the following operations are performed
1. Close file
2. Open file
3. truncate file
4. append file
was:
In the cluster version 3.2.0 production environment，
We found that due to edit log corruption, Standby NameNode could not properly
load the Ediltog log, result in abnormal exit of the service and failure to
restart
> Due to edit log corruption, Standby NameNode could not properly load the
> Ediltog log, result in abnormal exit of the service and failure to restart
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-15391
> URL: https://issues.apache.org/jira/browse/HDFS-15391
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.2.0
> Reporter: huhaiyang
> Priority: Critical
>
> In the cluster version 3.2.0 production environment，
> We found that due to edit log corruption, Standby NameNode could not
> properly load the Ediltog log, result in abnormal exit of the service and
> failure to restart
>
> The specific scenario is that Flink writes to HDFS, and in the case of an
> exception to the write file, the following operations are performed
> 1. Close file
> 2. Open file
> 3. truncate file
> 4. append file
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
