You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2010/03/09 14:34:27 UTC
[jira] Created: (HADOOP-6624) Hadoop conf/ servlet is serving up an
invalid JSON file
Hadoop conf/ servlet is serving up an invalid JSON file
-------------------------------------------------------
Key: HADOOP-6624
URL: https://issues.apache.org/jira/browse/HADOOP-6624
Project: Hadoop Common
Issue Type: Bug
Components: conf
Affects Versions: 0.22.0
Environment: Suse, Java 6, virtual infrastructure.
Reporter: Steve Loughran
Priority: Minor
Seeing this on a machine hosting both the NN and JT. The NN's conf/ servlet works as both XML and JSON, but the JT's conf is only coming back as XML, when I ask for JSON I see
{code}
{"properties":[
{code}
To make sure nothing was interfering I connected to the box, did a direct telnet
{code}
masterc0-vif0:~ # telnet masterc0-vif0 50030
Trying 10.144.175.2...
Connected to masterc0-vif0.
Escape character is '^]'.
GET /conf?format=json HTTP/1.0
HTTP/1.1 200 OK
Content-Type: text/javascript; charset=utf-8
Server: Jetty(6.1.14)
{"properties":[Connection closed by foreign host.
masterc0-vif0:~ #
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6624) Hadoop conf/ servlet is serving up
an invalid JSON file
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843044#action_12843044 ]
Steve Loughran commented on HADOOP-6624:
----------------------------------------
It may make sense to write the props to a buffer and then include a content-length header, make it easier for things to detect breakage en-route, proxy servers playing up, etc, etc.
> Hadoop conf/ servlet is serving up an invalid JSON file
> -------------------------------------------------------
>
> Key: HADOOP-6624
> URL: https://issues.apache.org/jira/browse/HADOOP-6624
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.22.0
> Environment: Suse, Java 6, virtual infrastructure.
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: jtconf.xml
>
>
> Seeing this on a machine hosting both the NN and JT. The NN's conf/ servlet works as both XML and JSON, but the JT's conf is only coming back as XML, when I ask for JSON I see
> {code}
> {"properties":[
> {code}
> To make sure nothing was interfering I connected to the box, did a direct telnet
> {code}
> masterc0-vif0:~ # telnet masterc0-vif0 50030
> Trying 10.144.175.2...
> Connected to masterc0-vif0.
> Escape character is '^]'.
> GET /conf?format=json HTTP/1.0
> HTTP/1.1 200 OK
> Content-Type: text/javascript; charset=utf-8
> Server: Jetty(6.1.14)
> {"properties":[Connection closed by foreign host.
> masterc0-vif0:~ #
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6624) Hadoop conf/ servlet is serving up an
invalid JSON file
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-6624:
-----------------------------------
Attachment: jtconf.xml
This is the XML file served up; it's been dynamically put together by merging in stuff with the main hadoop-common config, hence various constants. No obvious reason why it shouldn't be served up.
If I could find the logs, I'd see what they were saying.
> Hadoop conf/ servlet is serving up an invalid JSON file
> -------------------------------------------------------
>
> Key: HADOOP-6624
> URL: https://issues.apache.org/jira/browse/HADOOP-6624
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.22.0
> Environment: Suse, Java 6, virtual infrastructure.
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: jtconf.xml
>
>
> Seeing this on a machine hosting both the NN and JT. The NN's conf/ servlet works as both XML and JSON, but the JT's conf is only coming back as XML, when I ask for JSON I see
> {code}
> {"properties":[
> {code}
> To make sure nothing was interfering I connected to the box, did a direct telnet
> {code}
> masterc0-vif0:~ # telnet masterc0-vif0 50030
> Trying 10.144.175.2...
> Connected to masterc0-vif0.
> Escape character is '^]'.
> GET /conf?format=json HTTP/1.0
> HTTP/1.1 200 OK
> Content-Type: text/javascript; charset=utf-8
> Server: Jetty(6.1.14)
> {"properties":[Connection closed by foreign host.
> masterc0-vif0:~ #
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6624) Hadoop conf/ servlet is serving up an
invalid JSON file
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-6624:
-----------------------------------
Attachment: nnconf.json
For comparison, the namenode configuration as JSON.
> Hadoop conf/ servlet is serving up an invalid JSON file
> -------------------------------------------------------
>
> Key: HADOOP-6624
> URL: https://issues.apache.org/jira/browse/HADOOP-6624
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.22.0
> Environment: Suse, Java 6, virtual infrastructure.
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: jtconf.xml, nnconf.json
>
>
> Seeing this on a machine hosting both the NN and JT. The NN's conf/ servlet works as both XML and JSON, but the JT's conf is only coming back as XML, when I ask for JSON I see
> {code}
> {"properties":[
> {code}
> To make sure nothing was interfering I connected to the box, did a direct telnet
> {code}
> masterc0-vif0:~ # telnet masterc0-vif0 50030
> Trying 10.144.175.2...
> Connected to masterc0-vif0.
> Escape character is '^]'.
> GET /conf?format=json HTTP/1.0
> HTTP/1.1 200 OK
> Content-Type: text/javascript; charset=utf-8
> Server: Jetty(6.1.14)
> {"properties":[Connection closed by foreign host.
> masterc0-vif0:~ #
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.