[
https://issues.apache.org/jira/browse/HDFS-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389198#comment-14389198
]
Allen Wittenauer commented on HDFS-7991:
----------------------------------------
bq. But it's hard to know if the NN is still doing checkpoint or NN is stuck in
somewhere else.
Why can't we ask via REST?
bq. can we just simply capture the value of HADOOP_OPTS before appending
HADOOP_NAMENODE_OPTS to it, and use the captured value for this checkpoint?
Possible? Maybe. Simply? no. It's going to get very messy because you need to
juggle pretty much the entire shell state: HADOOP_CLIENT_OPTS, _finalize,
logfile settings, etc, all need to get saved off and/or manipulated in order to
provide the same/similar execution environment that dfsadmin uses... and that's
before we even talk about what happens with custom shell profiles.
bq. Looks like this way equals to using a dfsadmin command in the NN's machine.
It might look that way at the Java level, but at the shell level it's going to
be chaos. It will definitely cause all sorts of problems given how open the
shell level has always been.
> 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
>
>
> 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)
