[
https://issues.apache.org/jira/browse/HDFS-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556434#comment-14556434
]
Allen Wittenauer edited comment on HDFS-7991 at 5/22/15 4:57 PM:
-----------------------------------------------------------------
bq. Any thoughts?
Just one, and this is the line that triggered it:
bq. Instead of doing everything at the end while stopping, why not implement a
periodic check inside Active NameNode itself to check for the checkpoint.
I've been working under the assumption that the sites that are hitting this
issue are running a secondary namenode. Is that not true? Doesn't the 2NN
make this whole issue go away?
* If the answer is "The 2NN does make this issue go away" then this is a "won't
fix" and we should yank out the broken bash code that's presently in trunk and
causes my stop's to actually *fail*.
* If the answer is "No, the 2NN has nothing to do with this" then
[~vinayrpet]'s suggestion (either separate or combined with the 2NN) is a MUCH
better answer than hacking the hell out of this stuff.
was (Author: aw):
bq. Any thoughts?
Just one, and this is the line that triggered it:
bq. Instead of doing everything at the end while stopping, why not implement a
periodic check inside Active NameNode itself to check for the checkpoint.
I've been working under the assumption that the sites that are hitting this
issue are running a secondary namenode. Is that not true? Doesn't the 2NN
make this whole issue go away?
* If the answer is "The 2NN does make this issue go away" then this is a "won't
fix" and we should yank out the broken bash code that's presently in trunk and
causes my stop's to actually *fail*.
* If the answer is "No, the 2NN has nothing to do with this" then [~vinayrpet]
(either separate or combined with the 2NN) is a MUCH better answer than hacking
the hell out of this stuff.
> 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-shellpart.patch, 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)
