[
https://issues.apache.org/jira/browse/HDFS-16869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Ma updated HDFS-16869:
-----------------------------
Description:
We first encounter this issue in 3.3.1 version when we are upgrading from 3.1.1
to 3.3.1 which may cause NameNode start failure but just occasionally not
everytime.
The root cause for why 0 size of clientid happened here is still not found
after long-term investigating.
So here we add a protection judge here to exlude 0 size of clientid from be
added into cache.
was:
The root cause for why 0 size of clientid happened here is still not found.
So here we add a protection judge here to exlude 0 size of clientid from be
added into cache.
> Fail to start namenode owing to 0 size of clientid recorded in edit log.
> ------------------------------------------------------------------------
>
> Key: HDFS-16869
> URL: https://issues.apache.org/jira/browse/HDFS-16869
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.3.1, 3.3.2, 3.3.3, 3.3.4
> Reporter: Daniel Ma
> Assignee: Daniel Ma
> Priority: Major
>
> We first encounter this issue in 3.3.1 version when we are upgrading from
> 3.1.1 to 3.3.1 which may cause NameNode start failure but just occasionally
> not everytime.
> The root cause for why 0 size of clientid happened here is still not found
> after long-term investigating.
> So here we add a protection judge here to exlude 0 size of clientid from be
> added into cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
