[
https://issues.apache.org/jira/browse/HDFS-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555112#comment-14555112
]
Suresh Srinivas edited comment on HDFS-7991 at 5/21/15 9:56 PM:
----------------------------------------------------------------
bq. bash code sees exit with failure and sends kill -9.
I think the goal of this jira should be to ensure save namespace is done when
editlog size is huge. I have seen many cases where people either had to suffer
loss of data or wait for more than 3 days for namenode to startup consuming all
the pending editlogs.
Blindly sending kill -9 is not an option in my opinion. Instead of emphasizing
namenode stop functionality works, I would rather see save namespace work.
Isn't there an environment variable that enables this functionality? For folks
who want stop to not save namespace or a different behavior, it can be be used
to go back to the previous behavior, right?
was (Author: sureshms):
bq. bash code sees exit with failure and sends kill -9.
I think the goal of this jira should be to ensure save namespace is done when
editlog size is huge. I have seen many cases where people either had to suffer
loss of data or wait for more than 3 days for namenode to startup consuming all
the pending editlogs.
Blindly sending kill -9 is not an option in my opinion. Instead of emphasizing
namenode stop functionality works, I would rather see save namespace work.
Isn't there an environment variable that enables this functionality? For folks
who want stop to no save namespace or a different behavior, it can be be used
to go back to the previous behavior, right?
> Allow users to skip checkpoint when stopping NameNode
> -----------------------------------------------------
>
> Key: HDFS-7991
> URL: https://issues.apache.org/jira/browse/HDFS-7991
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-7991.000.patch, HDFS-7991.001.patch,
> HDFS-7991.002.patch, HDFS-7991.003.patch, HDFS-7991.004.patch
>
>
> This is a follow-up jira of HDFS-6353. HDFS-6353 adds the functionality to
> check if saving namespace is necessary before stopping namenode. As [~kihwal]
> pointed out in this
> [comment|https://issues.apache.org/jira/browse/HDFS-6353?focusedCommentId=14380898&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14380898],
> in a secured cluster this new functionality requires the user to be kinit'ed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
