[jira] Reopened: (HADOOP-6281) HtmlQuoting throws NullPointerException
[
https://issues.apache.org/jira/browse/HADOOP-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gary murry reopened HADOOP-6281:
HtmlQuoting throws NullPointerException
---
Key: HADOOP-6281
URL: https://issues.apache.org/jira/browse/HADOOP-6281
Project: Hadoop Common
Issue Type: Bug
Reporter: Tsz Wo (Nicholas), SZE
Assignee: Owen O'Malley
Fix For: 0.21.0
Attachments: h-6281.patch
{noformat}
java.lang.NullPointerException
at
org.apache.hadoop.http.HtmlQuoting.quoteHtmlChars(HtmlQuoting.java:95)
at
org.apache.hadoop.http.HttpServer$QuotingInputFilter$RequestQuoter.getParameter(HttpServer.java:570)
at
org.apache.hadoop.hdfs.server.namenode.NamenodeJspHelper$HealthJsp.generateHealthReport(NamenodeJspHelper.java:168)
at
org.apache.hadoop.hdfs.server.namenode.dfshealth_jsp._jspService(dfshealth_jsp.java:96)
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: different modes of inter process communication
Steve Loughran wrote: Raghu Angadi wrote: A heartBeat is also an RPC. When you pause Namenode for 30 sec the datanode's heartbeat thread just waits for 30 sec for its heartbeat RPC to return. Note that when you pause Namenode, the RPCs to it don't fail immediately. During this wait, DNs can perform other transactions like serving data to clients. If the heartbeat were just telling the NN that the DN is alive, Thats not the case in Hadoop. Central servers don't actively contact their slaves. It's been a long standing problem. For e.g. anything that NN want to tell a DN, it has to be in the form of response to a heartbeat or another RPC. Raghu. you could do it with a UDP that didn't block the DN. If, however, the DN needs to know/care that the NN is up, then you do need to care about the state of the namenode. But you don't have to do it blocking; looking for a UDP back some time later is all you need to do.
Re: Towards Hadoop 1.0: Stronger API Compatibility from 0.21 onwards
On 9/25/09 10:13 AM, Dhruba Borthakur dhr...@gmail.com wrote: It is really nice to have wire-compatibility between clients and servers running different versions of hadoop. The reason we would like this is because we can allow the same client (Hive, etc) submit jobs to two different clusters running different versions of hadoop. But I am not stuck up on the name of the release that supports wire-compatibility, it can be either 1.0 or something later than that. To me, the lack of wire compatibility makes will make Hadoop 1.0 in name only when in reality it is more like 0.80. :(
Re: Towards Hadoop 1.0: Stronger API Compatibility from 0.21 onwards
On Sep 25, 2009, at 12:03 PM, Allen Wittenauer wrote: On 9/25/09 10:13 AM, Dhruba Borthakur dhr...@gmail.com wrote: It is really nice to have wire-compatibility between clients and servers running different versions of hadoop. The reason we would like this is because we can allow the same client (Hive, etc) submit jobs to two different clusters running different versions of hadoop. But I am not stuck up on the name of the release that supports wire-compatibility, it can be either 1.0 or something later than that. To me, the lack of wire compatibility makes will make Hadoop 1.0 in name only when in reality it is more like 0.80. :( My sentiments exactly, though I could learn to live with it
Re: Towards Hadoop 1.0: Stronger API Compatibility from 0.21 onwards
On 9/25/09 12:44 PM, Sanjay Radia sra...@yahoo-inc.com wrote: On Sep 25, 2009, at 12:03 PM, Allen Wittenauer wrote: On 9/25/09 10:13 AM, Dhruba Borthakur dhr...@gmail.com wrote: It is really nice to have wire-compatibility between clients and servers running different versions of hadoop. The reason we would like this is because we can allow the same client (Hive, etc) submit jobs to two different clusters running different versions of hadoop. But I am not stuck up on the name of the release that supports wire-compatibility, it can be either 1.0 or something later than that. To me, the lack of wire compatibility makes will make Hadoop 1.0 in name only when in reality it is more like 0.80. :( My sentiments exactly, though I could learn to live with it We just had this discussion today about how to put Hadoop into a production pipeline. I was under the impression that 1.0 was going to be wire compatible too. This is just so disappointing and, quite frankly, makes 1.0 less than useful for Real Work. Great, the APIs don't change but you still have the same problems of getting data on/off the grid without upgrading your clients every time. To me, without wire compatibility, 1.0 makes me feel pretty meh; who cares--we're still going to be in upgrade hell.
