[jira] [Assigned] (HADOOP-7730) Allow TestCLI to be run against a cluster
[ https://issues.apache.org/jira/browse/HADOOP-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik reassigned HADOOP-7730: -- Assignee: Konstantin Boudnik > Allow TestCLI to be run against a cluster > - > > Key: HADOOP-7730 > URL: https://issues.apache.org/jira/browse/HADOOP-7730 > Project: Hadoop Common > Issue Type: Test > Components: test >Affects Versions: 0.22.0 >Reporter: Konstantin Boudnik >Assignee: Konstantin Boudnik > Attachments: HADOOP-7730.patch > > > Use the same CLI test to test cluster bits (see HDFS-1762 for more info) -- 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] (HADOOP-7730) Allow TestCLI to be run against a cluster
[ https://issues.apache.org/jira/browse/HADOOP-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-7730: --- Attachment: HADOOP-7730.patch Moving common patch from hdfs ticket. > Allow TestCLI to be run against a cluster > - > > Key: HADOOP-7730 > URL: https://issues.apache.org/jira/browse/HADOOP-7730 > Project: Hadoop Common > Issue Type: Test > Components: test >Affects Versions: 0.22.0 >Reporter: Konstantin Boudnik > Attachments: HADOOP-7730.patch > > > Use the same CLI test to test cluster bits (see HDFS-1762 for more info) -- 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] [Created] (HADOOP-7730) Allow TestCLI to be run against a cluster
Allow TestCLI to be run against a cluster - Key: HADOOP-7730 URL: https://issues.apache.org/jira/browse/HADOOP-7730 Project: Hadoop Common Issue Type: Test Components: test Affects Versions: 0.22.0 Reporter: Konstantin Boudnik Use the same CLI test to test cluster bits (see HDFS-1762 for more info) -- 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] (HADOOP-7729) Send back valid HTTP response if user hits IPC port with HTTP GET
[ https://issues.apache.org/jira/browse/HADOOP-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123617#comment-13123617 ] Hadoop QA commented on HADOOP-7729: --- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12498334/hadoop-7729.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/280//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/280//console This message is automatically generated. > Send back valid HTTP response if user hits IPC port with HTTP GET > - > > Key: HADOOP-7729 > URL: https://issues.apache.org/jira/browse/HADOOP-7729 > Project: Hadoop Common > Issue Type: Improvement > Components: ipc >Affects Versions: 0.23.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon > Attachments: hadoop-7729.txt > > > Often, I've seen users get confused between the IPC ports and HTTP ports for > a daemon. It would be easy for us to detect when an HTTP GET request hits an > IPC port, and instead of sending back garbage, we can send back a valid HTTP > response explaining their mistake. -- 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] (HADOOP-7729) Send back valid HTTP response if user hits IPC port with HTTP GET
[ https://issues.apache.org/jira/browse/HADOOP-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-7729: Attachment: hadoop-7729.txt > Send back valid HTTP response if user hits IPC port with HTTP GET > - > > Key: HADOOP-7729 > URL: https://issues.apache.org/jira/browse/HADOOP-7729 > Project: Hadoop Common > Issue Type: Improvement > Components: ipc >Affects Versions: 0.23.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon > Attachments: hadoop-7729.txt > > > Often, I've seen users get confused between the IPC ports and HTTP ports for > a daemon. It would be easy for us to detect when an HTTP GET request hits an > IPC port, and instead of sending back garbage, we can send back a valid HTTP > response explaining their mistake. -- 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] (HADOOP-7729) Send back valid HTTP response if user hits IPC port with HTTP GET
[ https://issues.apache.org/jira/browse/HADOOP-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-7729: Status: Patch Available (was: Open) > Send back valid HTTP response if user hits IPC port with HTTP GET > - > > Key: HADOOP-7729 > URL: https://issues.apache.org/jira/browse/HADOOP-7729 > Project: Hadoop Common > Issue Type: Improvement > Components: ipc >Affects Versions: 0.23.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon > Attachments: hadoop-7729.txt > > > Often, I've seen users get confused between the IPC ports and HTTP ports for > a daemon. It would be easy for us to detect when an HTTP GET request hits an > IPC port, and instead of sending back garbage, we can send back a valid HTTP > response explaining their mistake. -- 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] [Created] (HADOOP-7729) Send back valid HTTP response if user hits IPC port with HTTP GET
Send back valid HTTP response if user hits IPC port with HTTP GET - Key: HADOOP-7729 URL: https://issues.apache.org/jira/browse/HADOOP-7729 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 0.23.0 Reporter: Todd Lipcon Assignee: Todd Lipcon Often, I've seen users get confused between the IPC ports and HTTP ports for a daemon. It would be easy for us to detect when an HTTP GET request hits an IPC port, and instead of sending back garbage, we can send back a valid HTTP response explaining their mistake. -- 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] (HADOOP-7627) Improve MetricsAsserts to give more understandable output on failure
[ https://issues.apache.org/jira/browse/HADOOP-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123494#comment-13123494 ] Hudson commented on HADOOP-7627: Integrated in Hadoop-Mapreduce-trunk #854 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/854/]) HADOOP-7627. Improve MetricsAsserts to give more understandable output on failure. Contributed by Todd Lipcon. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180259 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/test/MetricsAsserts.java > Improve MetricsAsserts to give more understandable output on failure > > > Key: HADOOP-7627 > URL: https://issues.apache.org/jira/browse/HADOOP-7627 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics, test >Affects Versions: 0.23.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 0.23.0 > > Attachments: hadoop-7627.txt > > > In developing a test case that uses MetricsAsserts, I had two issues: > 1) the error output in the case that an assertion failed does not currently > give any information as to the _actual_ value of the metric > 2) there is no way to retrieve the metric variable (eg to assert that the sum > of a metric over all DNs is equal to some value) > This JIRA is to improve this test class to fix the above issues. -- 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] (HADOOP-7627) Improve MetricsAsserts to give more understandable output on failure
[ https://issues.apache.org/jira/browse/HADOOP-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123485#comment-13123485 ] Hudson commented on HADOOP-7627: Integrated in Hadoop-Mapreduce-0.23-Build #40 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/40/]) HADOOP-7627. Improve MetricsAsserts to give more understandable output on failure. Contributed by Todd Lipcon. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180258 Files : * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/test/MetricsAsserts.java > Improve MetricsAsserts to give more understandable output on failure > > > Key: HADOOP-7627 > URL: https://issues.apache.org/jira/browse/HADOOP-7627 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics, test >Affects Versions: 0.23.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 0.23.0 > > Attachments: hadoop-7627.txt > > > In developing a test case that uses MetricsAsserts, I had two issues: > 1) the error output in the case that an assertion failed does not currently > give any information as to the _actual_ value of the metric > 2) there is no way to retrieve the metric variable (eg to assert that the sum > of a metric over all DNs is equal to some value) > This JIRA is to improve this test class to fix the above issues. -- 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] (HADOOP-7627) Improve MetricsAsserts to give more understandable output on failure
[ https://issues.apache.org/jira/browse/HADOOP-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123472#comment-13123472 ] Hudson commented on HADOOP-7627: Integrated in Hadoop-Hdfs-0.23-Build #33 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/33/]) HADOOP-7627. Improve MetricsAsserts to give more understandable output on failure. Contributed by Todd Lipcon. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180258 Files : * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/test/MetricsAsserts.java > Improve MetricsAsserts to give more understandable output on failure > > > Key: HADOOP-7627 > URL: https://issues.apache.org/jira/browse/HADOOP-7627 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics, test >Affects Versions: 0.23.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 0.23.0 > > Attachments: hadoop-7627.txt > > > In developing a test case that uses MetricsAsserts, I had two issues: > 1) the error output in the case that an assertion failed does not currently > give any information as to the _actual_ value of the metric > 2) there is no way to retrieve the metric variable (eg to assert that the sum > of a metric over all DNs is equal to some value) > This JIRA is to improve this test class to fix the above issues. -- 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] (HADOOP-7627) Improve MetricsAsserts to give more understandable output on failure
[ https://issues.apache.org/jira/browse/HADOOP-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123454#comment-13123454 ] Hudson commented on HADOOP-7627: Integrated in Hadoop-Hdfs-trunk #824 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/824/]) HADOOP-7627. Improve MetricsAsserts to give more understandable output on failure. Contributed by Todd Lipcon. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180259 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/test/MetricsAsserts.java > Improve MetricsAsserts to give more understandable output on failure > > > Key: HADOOP-7627 > URL: https://issues.apache.org/jira/browse/HADOOP-7627 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics, test >Affects Versions: 0.23.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 0.23.0 > > Attachments: hadoop-7627.txt > > > In developing a test case that uses MetricsAsserts, I had two issues: > 1) the error output in the case that an assertion failed does not currently > give any information as to the _actual_ value of the metric > 2) there is no way to retrieve the metric variable (eg to assert that the sum > of a metric over all DNs is equal to some value) > This JIRA is to improve this test class to fix the above issues. -- 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] (HADOOP-7727) fix some typos and tabs in CHANGES.TXT
[ https://issues.apache.org/jira/browse/HADOOP-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123455#comment-13123455 ] Hudson commented on HADOOP-7727: Integrated in Hadoop-Hdfs-trunk #824 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/824/]) HADOOP-7727 fix some typos and tabs in CHANGES.TXT stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180019 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt > fix some typos and tabs in CHANGES.TXT > -- > > Key: HADOOP-7727 > URL: https://issues.apache.org/jira/browse/HADOOP-7727 > Project: Hadoop Common > Issue Type: Improvement > Components: build >Affects Versions: 0.24.0 >Reporter: Steve Loughran >Assignee: Steve Loughran >Priority: Trivial > Fix For: 0.24.0 > > Attachments: minor-changes-txt-typos.patch > > Original Estimate: 1m > Remaining Estimate: 1m > > This is a minor edit to CHANGES.txt; giving it a JIRA issue to have complete > release notes (though I'm not going to add it to the CHANGES.txt file as that > would be too recursive). There are a couple of tabs and mis-spelling of the > word exception in the trunk CHANGES.TXT -- 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] (HADOOP-7688) When a servlet filter throws an exception in init(..), the Jetty server failed silently.
[ https://issues.apache.org/jira/browse/HADOOP-7688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123441#comment-13123441 ] Uma Maheswara Rao G commented on HADOOP-7688: - Thanks a lot for taking a look! Sorry for the late in reply. I was on sudden leave. will take up my tasks from this Monday. I did not find any configuration item for controlling of Filter loading. I know we can control the Servlet loading by using load-on-startup property. I think Filter init methods will be called when loading the web contexts (or APPS). In this case, When loading the web contexts, if Filter init api throws any exception, application loading is failing. Because of one application load failure, server can not be shutdown in ideal case. So, it is just continuing. When first request comes, it is giving 503 response. In Ideal case server should not shutdown, so it is continuing. But in Hadoop specific case i think we can thow exception if any of the context loading fails. Nicholas, can you please give your opinion as well? Thanks Uma > When a servlet filter throws an exception in init(..), the Jetty server > failed silently. > - > > Key: HADOOP-7688 > URL: https://issues.apache.org/jira/browse/HADOOP-7688 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Uma Maheswara Rao G > Attachments: filter-init-exception-test.patch, > org.apache.hadoop.http.TestServletFilter-output.txt > > > When a servlet filter throws a ServletException in init(..), the exception is > logged by Jetty but not re-throws to the caller. As a result, the Jetty > server failed silently. -- 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
