from namenode:live.dfs.http.address, work out the path to the health page:
http://127.0.0.1:8021/webapps/hdfs/dfshealth.jsp
(LAZY namenode:ive.dfs.http.address ++ "/webapps/hdfs/dfshealth.jsp" )
and ping it
Steve Loughran added a comment - 04/Feb/09 05:03 PM (GMT) when deployed to a separate host, I'm seeing a 404 response here.
Possibilities: no JSP handling
09/02/04 17:02:10 [140558636@qtp0-0] WARN servlet.JspServlet : PWC6117: File "/tmp/Jetty_localhost_8021_hdfs____xav36j/webapp/webapps/hdfs/dfshealth.jsp" not found
09/02/04 17:02:12 [ExtDataNode] INFO datanode.DataNode : BlockReport of 0 blocks got processed in 1 msecs
They are right: the file is not there. There's no JSP binding.
Options:
1. include **.jsp in our hadoop JAR
2. find out what is wrong with the webapp registration
Improvement
Resolved
Major
add test for dfshealth on the filesystem
Possibilities: no JSP handling
09/02/04 17:02:10 [140558636@qtp0-0] WARN servlet.JspServlet : PWC6117: File "/tmp/Jetty_localhost_8021_hdfs____xav36j/webapp/webapps/hdfs/dfshealth.jsp" not found
09/02/04 17:02:12 [ExtDataNode] INFO datanode.DataNode : BlockReport of 0 blocks got processed in 1 msecs
They are right: the file is not there. There's no JSP binding.
Options:
1. include **.jsp in our hadoop JAR
2. find out what is wrong with the webapp registration