[ https://issues.apache.org/jira/browse/HDFS-15421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146211#comment-17146211 ]
Takanobu Asanuma commented on HDFS-15421: ----------------------------------------- Thanks for your explanation, [~shv]. After thinking about it again, my concern is already covered by HDFS-14941. Surely Standby NN should not update the global GS in OP_REASSIGN_LEASE. Sorry for confusing you, [~aajisaka]. I agree that HDFS-14941 and HDFS-15421.004.patch cover all the cases. I'm +1 on [^HDFS-15421.004.patch]. > IBR leak causes standby NN to be stuck in safe mode > --------------------------------------------------- > > Key: HDFS-15421 > URL: https://issues.apache.org/jira/browse/HDFS-15421 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Reporter: Kihwal Lee > Assignee: Akira Ajisaka > Priority: Blocker > Labels: release-blocker > Attachments: HDFS-15421-000.patch, HDFS-15421-001.patch, > HDFS-15421.002.patch, HDFS-15421.003.patch, HDFS-15421.004.patch, > HDFS-15421.005.patch, HDFS-15421.006.patch, HDFS-15421.007.patch > > > After HDFS-14941, update of the global gen stamp is delayed in certain > situations. This makes the last set of incremental block reports from append > "from future", which causes it to be simply re-queued to the pending DN > message queue, rather than processed to complete the block. The last set of > IBRs will leak and never cleaned until it transitions to active. The size of > {{pendingDNMessages}} constantly grows until then. > If a leak happens while in a startup safe mode, the namenode will never be > able to come out of safe mode on its own. -- 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