[jira] [Commented] (HDFS-2978) The NameNode should expose name dir statuses via JMX
[ https://issues.apache.org/jira/browse/HDFS-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13216160#comment-13216160 ] Hitesh Shah commented on HDFS-2978: --- @Aaron, Minor question on the use of emitting the data as a json-encoded string - any reason why this is being done for all the information exposed through the mbeans instead of using defined structures which are recognized and handled by the JMX interface in any case? Also, ignoring the above comment, would it be a good idea to have this available in 1.x too? The NameNode should expose name dir statuses via JMX Key: HDFS-2978 URL: https://issues.apache.org/jira/browse/HDFS-2978 Project: Hadoop HDFS Issue Type: New Feature Components: name-node Affects Versions: 0.23.0 Reporter: Aaron T. Myers Assignee: Aaron T. Myers Attachments: HDFS-2978.patch We currently display this info on the NN web UI, so users who wish to monitor this must either do it manually or parse HTML. We should publish this information via JMX. -- 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-2978) The NameNode should expose name dir statuses via JMX
[ https://issues.apache.org/jira/browse/HDFS-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13216290#comment-13216290 ] Hitesh Shah commented on HDFS-2978: --- @Aaron, the current patch should be fine as all the data currently exposed follows the same json serialize approach. However, at some point, it would be good to look at exactly how this is being used or meant to be used and fix the mbean output if needed. Also to clarify, if the data is being read via the /jmx http endpoint, it will return a valid json object ( mapped from the object being returned to the MX bean interface ) but I am not sure how this will affect scripts/programs that access the jmx data via a local connection in terms of whether they need to be tightly bound to the object type being returned as compared to be being a more flexible in handling a serialized json string. The NameNode should expose name dir statuses via JMX Key: HDFS-2978 URL: https://issues.apache.org/jira/browse/HDFS-2978 Project: Hadoop HDFS Issue Type: New Feature Components: name-node Affects Versions: 0.23.0 Reporter: Aaron T. Myers Assignee: Aaron T. Myers Attachments: HDFS-2978.patch We currently display this info on the NN web UI, so users who wish to monitor this must either do it manually or parse HTML. We should publish this information via JMX. -- 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-2814) NamenodeMXBean does not account for svn revision in the version information
[ https://issues.apache.org/jira/browse/HDFS-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13189683#comment-13189683 ] Hitesh Shah commented on HDFS-2814: --- findbugs shows an error with org.apache.hadoop.hdfs.tools.GetConf$Command which does not seem to be related to the patch. audit warning seems to be due to hadoop-hdfs-project/hadoop-hdfs-httpfs/dev-support/findbugsExcludeFile.xml javadoc warnings also seem to be unrelated. NamenodeMXBean does not account for svn revision in the version information --- Key: HDFS-2814 URL: https://issues.apache.org/jira/browse/HDFS-2814 Project: Hadoop HDFS Issue Type: Improvement Affects Versions: 0.23.0, 1.0.0 Reporter: Hitesh Shah Priority: Minor Fix For: 0.23.1, 1.1.0 Attachments: HDFS-2814-branch-1.patch, HDFS-2814-trunk.patch Unlike the jobtracker where both the UI and jmx information report the version as x.y.z, rsvn revision, in case of the namenode, the UI displays x.y.z and svn revision info but the jmx output only contains the x.y.z version. -- 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-2816) Fix missing license header in hadoop-hdfs-project/hadoop-hdfs-httpfs/dev-support/findbugsExcludeFile.xml
[ https://issues.apache.org/jira/browse/HDFS-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13189988#comment-13189988 ] Hitesh Shah commented on HDFS-2816: --- Seen when working on HDFS-2814. Fix missing license header in hadoop-hdfs-project/hadoop-hdfs-httpfs/dev-support/findbugsExcludeFile.xml Key: HDFS-2816 URL: https://issues.apache.org/jira/browse/HDFS-2816 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.23.0, 0.24.0 Reporter: Hitesh Shah Priority: Trivial Fix For: 0.24.0, 0.23.1 Attachments: HDFS-2816.patch -- 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-442) dfsthroughput in test.jar throws NPE
[
https://issues.apache.org/jira/browse/HDFS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190242#comment-13190242
]
Hitesh Shah commented on HDFS-442:
--
+1. Patch looks good - hadoop.tmp.dir is always guaranteed to be set via
core-default. Tested with/without patch and fixes the issue.
dfsthroughput in test.jar throws NPE
Key: HDFS-442
URL: https://issues.apache.org/jira/browse/HDFS-442
Project: Hadoop HDFS
Issue Type: Bug
Components: test
Affects Versions: 0.20.1
Reporter: Ramya Sunil
Assignee: Harsh J
Priority: Minor
Attachments: HDFS-442.patch
On running hadoop jar hadoop-test.jar dfsthroughput OR hadoop
org.apache.hadoop.hdfs.BenchmarkThroughput, we get NullPointerException.
Below is the stacktrace:
{noformat}
Exception in thread main java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:394)
at java.util.Properties.setProperty(Properties.java:143)
at java.lang.System.setProperty(System.java:731)
at
org.apache.hadoop.hdfs.BenchmarkThroughput.run(BenchmarkThroughput.java:198)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hdfs.BenchmarkThroughput.main(BenchmarkThroughput.java:229)
{noformat}
--
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
