You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Bikas Saha (Created) (JIRA)" <ji...@apache.org> on 2012/02/08 00:51:01 UTC
[jira] [Created] (HDFS-2913) HA: Need a way to shutdown the Name
Node
HA: Need a way to shutdown the Name Node
----------------------------------------
Key: HDFS-2913
URL: https://issues.apache.org/jira/browse/HDFS-2913
Project: Hadoop HDFS
Issue Type: Sub-task
Components: name-node
Affects Versions: HA branch (HDFS-1623)
Reporter: Bikas Saha
Assignee: Bikas Saha
Ideally, NameNode.stop() needs to be called because it will change the HA state and shutdown all services. NameNode reference is not available anywhere. Hence it is not possible to shutdown the name node gracefully.
A possible solution could be to have a Service interface that gets passed down to components like FSNameSystem, via which they can inform the NameNode about irrecoverable errors. NameNode could then decide to shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2913) HA: Need a way to shutdown the Name
Node
Posted by "Todd Lipcon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HDFS-2913:
------------------------------
Issue Type: New Feature (was: Sub-task)
Parent: (was: HDFS-1623)
> HA: Need a way to shutdown the Name Node
> ----------------------------------------
>
> Key: HDFS-2913
> URL: https://issues.apache.org/jira/browse/HDFS-2913
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
> Ideally, NameNode.stop() needs to be called because it will change the HA state and shutdown all services. NameNode reference is not available anywhere. Hence it is not possible to shutdown the name node gracefully.
> A possible solution could be to have a Service interface that gets passed down to components like FSNameSystem, via which they can inform the NameNode about irrecoverable errors. NameNode could then decide to shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2913) HA: Need a way to shutdown the Name
Node
Posted by "Bikas Saha (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208683#comment-13208683 ]
Bikas Saha commented on HDFS-2913:
----------------------------------
There is currently no clean way to shutdown NN and we are using runtime.exit(). A clean shutdown might be useful in cases such as automatic failover when the active NN could pro-actively give up control and then terminate. In general, each component could ideally report its failure to NN and after that NN could decide whether to stop being active, go into safe mode or shut down completely. This JIRA tracks adding that framework.
This need not be under HA.
This is not critical to do, specially after runtime.exit solves HDFS-2912.
> HA: Need a way to shutdown the Name Node
> ----------------------------------------
>
> Key: HDFS-2913
> URL: https://issues.apache.org/jira/browse/HDFS-2913
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
> Ideally, NameNode.stop() needs to be called because it will change the HA state and shutdown all services. NameNode reference is not available anywhere. Hence it is not possible to shutdown the name node gracefully.
> A possible solution could be to have a Service interface that gets passed down to components like FSNameSystem, via which they can inform the NameNode about irrecoverable errors. NameNode could then decide to shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2913) HA: Need a way to shutdown the Name
Node
Posted by "Aaron T. Myers (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron T. Myers updated HDFS-2913:
---------------------------------
Component/s: ha
> HA: Need a way to shutdown the Name Node
> ----------------------------------------
>
> Key: HDFS-2913
> URL: https://issues.apache.org/jira/browse/HDFS-2913
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
> Ideally, NameNode.stop() needs to be called because it will change the HA state and shutdown all services. NameNode reference is not available anywhere. Hence it is not possible to shutdown the name node gracefully.
> A possible solution could be to have a Service interface that gets passed down to components like FSNameSystem, via which they can inform the NameNode about irrecoverable errors. NameNode could then decide to shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2913) HA: Need a way to shutdown the Name
Node
Posted by "Todd Lipcon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202997#comment-13202997 ]
Todd Lipcon commented on HDFS-2913:
-----------------------------------
Currently it is meant to do a "fail fast" shutdown -- i.e System.exit(1) after logging a FATAL message. A graceful shutdown would be a nice optimization, but HDFS-2912 should be treated as a bug that the expected fail-fast behavior isn't being triggered. Doing a graceful shutdown after hitting an unknown state is likely to be non-trivial
> HA: Need a way to shutdown the Name Node
> ----------------------------------------
>
> Key: HDFS-2913
> URL: https://issues.apache.org/jira/browse/HDFS-2913
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
> Ideally, NameNode.stop() needs to be called because it will change the HA state and shutdown all services. NameNode reference is not available anywhere. Hence it is not possible to shutdown the name node gracefully.
> A possible solution could be to have a Service interface that gets passed down to components like FSNameSystem, via which they can inform the NameNode about irrecoverable errors. NameNode could then decide to shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2913) HA: Need a way to shutdown the Name
Node
Posted by "Todd Lipcon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HDFS-2913:
------------------------------
Component/s: (was: ha)
Affects Version/s: (was: HA branch (HDFS-1623))
> HA: Need a way to shutdown the Name Node
> ----------------------------------------
>
> Key: HDFS-2913
> URL: https://issues.apache.org/jira/browse/HDFS-2913
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: name-node
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
> Ideally, NameNode.stop() needs to be called because it will change the HA state and shutdown all services. NameNode reference is not available anywhere. Hence it is not possible to shutdown the name node gracefully.
> A possible solution could be to have a Service interface that gets passed down to components like FSNameSystem, via which they can inform the NameNode about irrecoverable errors. NameNode could then decide to shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2913) HA: Need a way to shutdown the Name
Node
Posted by "Aaron T. Myers (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208207#comment-13208207 ]
Aaron T. Myers commented on HDFS-2913:
--------------------------------------
Hey Bikas, do you still intend to work on this? Seems like HDFS-2912 may have superseded this work.
> HA: Need a way to shutdown the Name Node
> ----------------------------------------
>
> Key: HDFS-2913
> URL: https://issues.apache.org/jira/browse/HDFS-2913
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
> Ideally, NameNode.stop() needs to be called because it will change the HA state and shutdown all services. NameNode reference is not available anywhere. Hence it is not possible to shutdown the name node gracefully.
> A possible solution could be to have a Service interface that gets passed down to components like FSNameSystem, via which they can inform the NameNode about irrecoverable errors. NameNode could then decide to shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2913) Add graceful shutdown command for the
NN
Posted by "Todd Lipcon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HDFS-2913:
------------------------------
Target Version/s: (was: HA branch (HDFS-1623))
Summary: Add graceful shutdown command for the NN (was: HA: Need a way to shutdown the Name Node)
Moved to be a non-HA-specific task, renamed to match the new purpose.
> Add graceful shutdown command for the NN
> ----------------------------------------
>
> Key: HDFS-2913
> URL: https://issues.apache.org/jira/browse/HDFS-2913
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: name-node
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
> Ideally, NameNode.stop() needs to be called because it will change the HA state and shutdown all services. NameNode reference is not available anywhere. Hence it is not possible to shutdown the name node gracefully.
> A possible solution could be to have a Service interface that gets passed down to components like FSNameSystem, via which they can inform the NameNode about irrecoverable errors. NameNode could then decide to shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira