[jira] [Commented] (HADOOP-8820) Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup)
[ https://issues.apache.org/jira/browse/HADOOP-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496030#comment-13496030 ] Tsz Wo (Nicholas), SZE commented on HADOOP-8820: Junping, thanks for the update. I also want to commit the HADOOP-8817 patch directly. However, some parts of the patch is not yet committed to trunk. Your original plan is to have separated patches for various components. I think it is a good plan since it is easier to review the patches. Why don't we stick with it? Jing, thanks for helping out here. Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup) --- Key: HADOOP-8820 URL: https://issues.apache.org/jira/browse/HADOOP-8820 Project: Hadoop Common Issue Type: New Feature Components: net Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-8820.b1.002.patch, HADOOP-8820.b1.003.patch, HADOOP-8820.patch This patch backport HADOOP-8469 and HADOOP-8470 to branch-1 and includes: 1. Make NetworkTopology class pluggable for extension. 2. Implement a 4-layer NetworkTopology class (named as NetworkTopologyWithNodeGroup) to use in virtualized environment (or other situation with additional layer between host and rack). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8820) Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup)
[ https://issues.apache.org/jira/browse/HADOOP-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496039#comment-13496039 ] Junping Du commented on HADOOP-8820: Nicholas, Thanks for comments and questions. Under your great help, most HDFS part of code is committed into trunk (except Balancer), so the left parts missing in trunk are mostly YARN. HADOOP-8817 patch is based on MRV1 which has less code change comparing with YARN and MapReduce part is already reviewed (by Luke). Also, I did a lot of tests on a deployed virtualized hadoop cluster for combined patch, so I think it could be better to commit these patches as a whole patch to get rid of potential bug involved by sync and could be convenient for the patch to go to release branch (branch-1.2?). What do you think? Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup) --- Key: HADOOP-8820 URL: https://issues.apache.org/jira/browse/HADOOP-8820 Project: Hadoop Common Issue Type: New Feature Components: net Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-8820.b1.002.patch, HADOOP-8820.b1.003.patch, HADOOP-8820.patch This patch backport HADOOP-8469 and HADOOP-8470 to branch-1 and includes: 1. Make NetworkTopology class pluggable for extension. 2. Implement a 4-layer NetworkTopology class (named as NetworkTopologyWithNodeGroup) to use in virtualized environment (or other situation with additional layer between host and rack). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8981) TestMetricsSystemImpl fails on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496046#comment-13496046 ] Ivan Mitic commented on HADOOP-8981: Seems to be a duplicate of HDFS-3636. TestMetricsSystemImpl fails on Windows -- Key: HADOOP-8981 URL: https://issues.apache.org/jira/browse/HADOOP-8981 Project: Hadoop Common Issue Type: Bug Components: metrics Affects Versions: trunk-win Reporter: Chris Nauroth Assignee: Arpit Agarwal The test is failing on an expected mock interaction. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8820) Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup)
[ https://issues.apache.org/jira/browse/HADOOP-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496055#comment-13496055 ] Jing Zhao commented on HADOOP-8820: --- bq. The 1st is not a issue as children is already checked before. I'm not sure if I understand the code correctly here. So the isRack() function first checks the children of the current node (if (getChildren().isEmpty())), but does not check the children of the first child of the current node. Thus is it possible that ((InnerNode) firstChild).children is empty (in which case the following get(0) may cause an IndexOutofBoundsException)? Or somewhere outside the function it has been checked? By the way, in the latest patch in HADOOP-8817 (HADOOP-8817-v3.patch), several method definitions seem to be repeated between BlockPlacementPolicy.java and BlockPlacementPolicyDefault.java (e.g., adjustSetsWithChosenReplica(), splitNodesWithLocalityGroup(), getLocalityGroupForSplit() and getRack()). So do we need to recheck the patch to verify? Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup) --- Key: HADOOP-8820 URL: https://issues.apache.org/jira/browse/HADOOP-8820 Project: Hadoop Common Issue Type: New Feature Components: net Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-8820.b1.002.patch, HADOOP-8820.b1.003.patch, HADOOP-8820.patch This patch backport HADOOP-8469 and HADOOP-8470 to branch-1 and includes: 1. Make NetworkTopology class pluggable for extension. 2. Implement a 4-layer NetworkTopology class (named as NetworkTopologyWithNodeGroup) to use in virtualized environment (or other situation with additional layer between host and rack). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8817) Backport Network Topology Extension for Virtualization (HADOOP-8468) to branch-1
[ https://issues.apache.org/jira/browse/HADOOP-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-8817: --- Attachment: HADOOP-8817-v4.patch Address Jing's comments with addressing one NPE issue and remove some redundant code. Backport Network Topology Extension for Virtualization (HADOOP-8468) to branch-1 Key: HADOOP-8817 URL: https://issues.apache.org/jira/browse/HADOOP-8817 Project: Hadoop Common Issue Type: Sub-task Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Labels: features Attachments: HADOOP-8817.patch, HADOOP-8817-v2.patch, HADOOP-8817-v3.patch, HADOOP-8817-v4.patch HADOOP-8468 propose network topology changes for running on virtualized infrastructure, which includes: 1. Add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup): HADOOP-8469, HADOOP-8470 2. Update Replica Placement/Removal Policy to reflect new topology layer: HDFS-3498, HDFS-3601 3. Update balancer policy:HDFS-3495 4. Update Task Scheduling Policy to reflect new topology layer and support the case that compute nodes (NodeManager or TaskTracker) and data nodes are separated into different VMs, but still benefit from physical host locality: YARN-18, YARN-19. This JIRA will address the backport work on branch-1 which will be divided into 4 issues/patches in related jira issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8820) Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup)
[ https://issues.apache.org/jira/browse/HADOOP-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496093#comment-13496093 ] Junping Du commented on HADOOP-8820: Hi,Jing. You are right that firstGrandChild is not checked before, I was thinking you are talking about firstChild. Also, the 4 methods you are listing here is just replicated. I already address your comments in v4 patch in HADOOP-8817. Thanks! Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup) --- Key: HADOOP-8820 URL: https://issues.apache.org/jira/browse/HADOOP-8820 Project: Hadoop Common Issue Type: New Feature Components: net Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-8820.b1.002.patch, HADOOP-8820.b1.003.patch, HADOOP-8820.patch This patch backport HADOOP-8469 and HADOOP-8470 to branch-1 and includes: 1. Make NetworkTopology class pluggable for extension. 2. Implement a 4-layer NetworkTopology class (named as NetworkTopologyWithNodeGroup) to use in virtualized environment (or other situation with additional layer between host and rack). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8860) Split MapReduce and YARN sections in documentation navigation
[ https://issues.apache.org/jira/browse/HADOOP-8860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496097#comment-13496097 ] Hudson commented on HADOOP-8860: Integrated in Hadoop-Yarn-trunk #35 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/35/]) Add new files missed from HADOOP-8860 commit. (Revision 1408288) Result = SUCCESS tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408288 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/resources * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/resources/css * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/site.xml * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/src/site/resources * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/src/site/resources/css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/resources * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/resources/css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/site.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/resources * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/resources/css * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/site.xml Split MapReduce and YARN sections in documentation navigation - Key: HADOOP-8860 URL: https://issues.apache.org/jira/browse/HADOOP-8860 Project: Hadoop Common Issue Type: Task Components: documentation Affects Versions: 2.0.1-alpha Reporter: Tom White Assignee: Tom White Fix For: 2.0.3-alpha Attachments: HADOOP-8860-23.patch, HADOOP-8860-23.sh, HADOOP-8860.patch, HADOOP-8860.patch, HADOOP-8860.sh, HADOOP-8860.sh This JIRA is to change the navigation on http://hadoop.apache.org/docs/r2.0.1-alpha/ to reflect the fact that MapReduce and YARN are separate modules/sub-projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9021) Enforce configured SASL method on the server
[ https://issues.apache.org/jira/browse/HADOOP-9021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496098#comment-13496098 ] Hudson commented on HADOOP-9021: Integrated in Hadoop-Yarn-trunk #35 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/35/]) HADOOP-9021. Enforce configured SASL method on the server (daryn via bobby) (Revision 1408473) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408473 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestSaslRPC.java Enforce configured SASL method on the server Key: HADOOP-9021 URL: https://issues.apache.org/jira/browse/HADOOP-9021 Project: Hadoop Common Issue Type: Sub-task Components: ipc, security Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0 Reporter: Daryn Sharp Assignee: Daryn Sharp Fix For: 3.0.0, 2.0.3-alpha Attachments: HADOOP-9021.patch, HADOOP-9021.patch The RPC needs to restrict itself to only using the configured SASL method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9022) Hadoop distcp tool fails to copy file if -m 0 specified
[ https://issues.apache.org/jira/browse/HADOOP-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496099#comment-13496099 ] Hudson commented on HADOOP-9022: Integrated in Hadoop-Yarn-trunk #35 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/35/]) HADOOP-9022. Hadoop distcp tool fails to copy file if -m 0 specified (Jonathan Eagles vai bobby) (Revision 1408488) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408488 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/DistCpOptions.java * /hadoop/common/trunk/hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/TestOptionsParser.java Hadoop distcp tool fails to copy file if -m 0 specified --- Key: HADOOP-9022 URL: https://issues.apache.org/jira/browse/HADOOP-9022 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.1, 0.23.3, 0.23.4 Reporter: Haiyang Jiang Assignee: Jonathan Eagles Fix For: 3.0.0, 2.0.3-alpha, 0.23.5 Attachments: HADOOP-9022.patch When trying to copy file using distcp on H23, if -m 0 is specified, distcp will just spawn 0 mapper tasks and the file will not be copied. But this used to work before H23, even when -m 0 specified, distcp will always copy the files. Checked the code of DistCp.java Before the rewrite, it set the number maps at least to 1 job.setNumMapTasks(Math.max(numMaps, 1)); But in the newest code, it just takes the input from user: job.getConfiguration().set(JobContext.NUM_MAPS, String.valueOf(inputOptions.getMaxMaps())); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9025) org.apache.hadoop.tools.TestCopyListing failing
[ https://issues.apache.org/jira/browse/HADOOP-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496105#comment-13496105 ] Hudson commented on HADOOP-9025: Integrated in Hadoop-Yarn-trunk #35 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/35/]) HADOOP-9025. org.apache.hadoop.tools.TestCopyListing failing. Contributed by Jonathan Eagles (Revision 1408604) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408604 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/TestCopyListing.java org.apache.hadoop.tools.TestCopyListing failing --- Key: HADOOP-9025 URL: https://issues.apache.org/jira/browse/HADOOP-9025 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0 Reporter: Robert Joseph Evans Assignee: Jonathan Eagles Fix For: 2.0.3-alpha, 0.23.5 Attachments: HADOOP-9025.patch https://builds.apache.org/job/PreCommit-HADOOP-Build/1732//testReport/org.apache.hadoop.tools/TestCopyListing/testDuplicates/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9022) Hadoop distcp tool fails to copy file if -m 0 specified
[ https://issues.apache.org/jira/browse/HADOOP-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496149#comment-13496149 ] Hudson commented on HADOOP-9022: Integrated in Hadoop-Hdfs-0.23-Build #434 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/434/]) svn merge -c 1408488 FIXES: HADOOP-9022. Hadoop distcp tool fails to copy file if -m 0 specified (Jonathan Eagles vai bobby) (Revision 1408493) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408493 Files : * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/DistCpOptions.java * /hadoop/common/branches/branch-0.23/hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/TestOptionsParser.java Hadoop distcp tool fails to copy file if -m 0 specified --- Key: HADOOP-9022 URL: https://issues.apache.org/jira/browse/HADOOP-9022 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.1, 0.23.3, 0.23.4 Reporter: Haiyang Jiang Assignee: Jonathan Eagles Fix For: 3.0.0, 2.0.3-alpha, 0.23.5 Attachments: HADOOP-9022.patch When trying to copy file using distcp on H23, if -m 0 is specified, distcp will just spawn 0 mapper tasks and the file will not be copied. But this used to work before H23, even when -m 0 specified, distcp will always copy the files. Checked the code of DistCp.java Before the rewrite, it set the number maps at least to 1 job.setNumMapTasks(Math.max(numMaps, 1)); But in the newest code, it just takes the input from user: job.getConfiguration().set(JobContext.NUM_MAPS, String.valueOf(inputOptions.getMaxMaps())); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9025) org.apache.hadoop.tools.TestCopyListing failing
[ https://issues.apache.org/jira/browse/HADOOP-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496153#comment-13496153 ] Hudson commented on HADOOP-9025: Integrated in Hadoop-Hdfs-0.23-Build #434 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/434/]) svn merge -c 1408604 FIXES: HADOOP-9025. org.apache.hadoop.tools.TestCopyListing failing. Contributed by Jonathan Eagles (Revision 1408606) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408606 Files : * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/TestCopyListing.java org.apache.hadoop.tools.TestCopyListing failing --- Key: HADOOP-9025 URL: https://issues.apache.org/jira/browse/HADOOP-9025 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0 Reporter: Robert Joseph Evans Assignee: Jonathan Eagles Fix For: 2.0.3-alpha, 0.23.5 Attachments: HADOOP-9025.patch https://builds.apache.org/job/PreCommit-HADOOP-Build/1732//testReport/org.apache.hadoop.tools/TestCopyListing/testDuplicates/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7397) Allow configurable timeouts when connecting to HDFS via java FileSystem API
[ https://issues.apache.org/jira/browse/HADOOP-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496166#comment-13496166 ] tuvantlp.com commented on HADOOP-7397: -- http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thanh lap doanh nghiep thành lập doanh nghiệp trọn gói thành lập doanh nghiệp như thế nào dịch vụ kế toán sổ sách kế toán báo cáo thuế http://tuvantlp.com/index.php/dich-vu-ke-toan-thue.html http://tuvantlp.com/index.php/dich-vu-ke-toan-thue.html http://tuvantlp.com/index.php/dich-vu-ke-toan-thue.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html Allow configurable timeouts when connecting to HDFS via java FileSystem API --- Key: HADOOP-7397 URL: https://issues.apache.org/jira/browse/HADOOP-7397 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 0.23.0 Reporter: Scott Fines Priority: Minor Labels: hadoop Attachments: HADOOP-7397.patch, timeout.patch If the NameNode is not available (in, for example, a network partition event separating the client from the NameNode), and an attempt is made to connect, then the FileSystem api will *eventually* timeout and throw an error. However, that timeout is currently hardcoded to be 20 seconds to connect, with 45 retries, for a total of a 15 minute wait before failure. While in many circumstances this is fine, there are also many circumstances (such as booting a service) where both the connection timeout and the number of retries should be significantly less, so as not to harm availability of other services. Investigating Client.java, I see that there are two fields in Connection: maxRetries and rpcTimeout. I propose either re-using those fields for initiating the connection as well; alternatively, using the already existing dfs.socket.timeout parameter to set the connection timeout on initialization, and potentially adding a new field such as dfs.connection.retries with a default of 45 to replicate current behaviors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7397) Allow configurable timeouts when connecting to HDFS via java FileSystem API
[ https://issues.apache.org/jira/browse/HADOOP-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496168#comment-13496168 ] tuvantlp.com commented on HADOOP-7397: -- http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/ http://tuvantlp.com/ http://tuvantlp.com/ http://tuvantlp.com/ http://tuvantlp.com/ Hướng dẫn thành lập doanh nghiệp Cần lưu ý những thông tin sau đây để tránh những sai sót rất dễ mắc phải khi soạn thảo hồ sơ thành lập doanh nghiệp: Xem bảng giá thành lập doanh nghiệp ở cuối bài này. 1. Chọn tên cho doanh nghiệp: (Khi thành lập doanh nghiệp phải chọn tên cho doanh nghiệp sao cho phù hợp với quy định và không được trùng tên, không gây nhầm lẫn với doanh nghiệp khác đã thành lập trước đó). Có thể kiểm tra tên doanh nghiệp ở Menu Nơi tra cứu thông tin: Dịch vụ thành lập doanh nghiệp, thành lập công ty. Những trường hợp sau đây được coi là gây nhầm lẫn với tên của các doanh nghiệp khác: a) Tên tiếng Việt, tên tiếng nước ngoài của doanh nghiệp dự định thành lập không được giống tên tiếng Việt, tên nước ngoài của doanh nghiệp khác đã thành lập trước đó. b) Tên của doanh nghiệp dự định thành lập chỉ khác tên của doanh nghiệp khác bởi ký hiệu ; ký hiệu - ; chữ và. c. Khi thành lập doanh nghiệp không đặt tên giống toàn bộ hay giống một phần của các cơ quan sau đây (trừ trường hợp có sự chấp thuận): Cơ quan nhà nước, Đơn vị lực lượng vũ trang nhân dân, Tên của tổ chức chính trị, tổ chức chính trị - xã hội. d. Không được sử dụng từ ngữ, ký hiệu vi phạm truyền thống lịch sử, văn hoá, đạo đức và thuần phong mỹ tục của dân tộc để đặt tên cho doanh nghiệp. e. Tên doanh nghiệp dự định thành lập không được giống tên thương mại của tổ chức, cá nhân khác đã đăng ký bảo hộ để cấu thành tên riêng của doanh nghiệp (trừ trường hợp được sự chấp thuận của chủ sở hữu). 2. Ngành, nghề kinh doanh của doanh nghiệp: (Trong giấy đề nghị đăng ký thành lập doanh nghiệp, yêu cầu ngành, nghề phải được mã hóa đến Cấp 4 theo Quyết định số 10/2007/QĐ-TTg ngày 23 tháng 01 năm 2007 của thủ Tướng Chính phủ). Sau khi thành lập, doanh nghiệp được quyền kinh doanh tất cả những ngành, nghề mà pháp luật không cấm. Nếu ngành, nghề kinh doanh yêu cầu có chứng chỉ hành nghề thì trong hồ sơ thành lập doanh nghiệp phải đính kèm chứng chỉ hành nghề sao y công chứng hoặc những giấy tờ cần thiết khác. Khi đăng ký thành lập doanh nghiệp cần lưu ý một số ngành, nghề yêu cầu phải có chứng chỉ hành nghề như: - Kinh doanh dịch vụ pháp lý. - Kinh doanh dịch vụ khám, chữa bệnh và kinh doanh dược phẩm. - Kinh doanh dịch vụ thú y, thuốc thú y. - Kinh doanh dịch vụ thiết kế quy hoạch xây dựng, khảo sát xây dựng, thiết kế xây dựng công trình, giám sát thi công xây dựng. - Kinh doanh dịch vụ kiểm toán. - Sản xuất, gia công, sang chai, đóng gói, mua bán thuốc bảo vệ thực vật. - Kinh doanh dịch vụ xông hơi khử trùng. - Kinh doanh dịch vụ thiết kế phương tiện vận tải. - Mua bán di vật, cổ vật, bảo vật quốc gia. - Kinh doanh dịch vụ kế toán. - Dịch vụ môi giới bất động sản, dịch vụ định giá bất động sản, dịch vụ sàn giao dịch bất động sản. Khi đăng ký thành lập doanh nghiệp cần lưu ý một số ngành, nghề yêu cầu phải có vốn pháp định như: (Vốn pháp định là số tiền tối thiểu bắt buộc phải có mới đủ điều kiện thành lập doanh nghiệp). - Tổ chức tín dụng, quỹ tín dụng nhân dân; tổ chức tín dụng phi ngân hàng. - Kinh doanh bất động sản. - Dịch vụ đòi nợ. - Dịch vụ đưa người lao động đi làm việc ở nước ngoài. - Sản xuất phim. - Cung cấp dịch vụ hàng không tại cảng hàng không. - Kinh doanh vận chuyển hàng không. - Kinh doanh vàng. Và một số ngành, nghề cấm kinh doanh: - Kinh doanh vũ khí quân dụng, trang thiết bị, kỹ thuật, khí tài, phương tiện chuyên dùng quân sự, công an. - Kinh doanh chất ma túy các loại. - Kinh doanh các sản phẩm văn hóa phản động, đồi trụy, mê tín dị đoan hoặc có hại tới giáo dục thẩm mỹ, nhân cách. - Kinh doanh các loại pháo. - Kinh doanh các loại đồ chơi, trò chơi nguy hiểm, đồ chơi, trò chơi có hại tới giáo dục nhân cách và sức khoẻ của trẻ em hoặc tới an ninh, trật tự an toàn xã hội. - Kinh doanh mại dâm, tổ chức mại dâm, buôn bán phụ nữ, trẻ em. - Kinh doanh dịch vụ tổ chức đánh bạc. - Kinh doanh dịch vụ điều tra bí mật xâm phạm lợi ích của Nhà nước, quyền và lợi ích hợp pháp của tổ chức, công dân. - Kinh doanh các loại phế liệu nhập khẩu gây ô nhiễm môi trường. - Kinh doanh các loại sản phẩm, hàng hoá và thiết bị cấm lưu hành, cấm sử dụng hoặc chưa được phép lưu hành/sử dụng tại Việt Nam. 3. Vốn điều lệ: + Vốn điều lệ là số vốn do các thành viên, cổ đông góp hoặc cam kết góp trong một thời hạn nhất định (được ghi rõ trong điều lệ của doanh nghiệp và giấy xin đăng
[jira] [Commented] (HADOOP-8860) Split MapReduce and YARN sections in documentation navigation
[ https://issues.apache.org/jira/browse/HADOOP-8860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496172#comment-13496172 ] Hudson commented on HADOOP-8860: Integrated in Hadoop-Hdfs-trunk #1225 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1225/]) Add new files missed from HADOOP-8860 commit. (Revision 1408288) Result = SUCCESS tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408288 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/resources * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/resources/css * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/site.xml * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/src/site/resources * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/src/site/resources/css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/resources * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/resources/css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/site.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/resources * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/resources/css * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/site.xml Split MapReduce and YARN sections in documentation navigation - Key: HADOOP-8860 URL: https://issues.apache.org/jira/browse/HADOOP-8860 Project: Hadoop Common Issue Type: Task Components: documentation Affects Versions: 2.0.1-alpha Reporter: Tom White Assignee: Tom White Fix For: 2.0.3-alpha Attachments: HADOOP-8860-23.patch, HADOOP-8860-23.sh, HADOOP-8860.patch, HADOOP-8860.patch, HADOOP-8860.sh, HADOOP-8860.sh This JIRA is to change the navigation on http://hadoop.apache.org/docs/r2.0.1-alpha/ to reflect the fact that MapReduce and YARN are separate modules/sub-projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9021) Enforce configured SASL method on the server
[ https://issues.apache.org/jira/browse/HADOOP-9021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496173#comment-13496173 ] Hudson commented on HADOOP-9021: Integrated in Hadoop-Hdfs-trunk #1225 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1225/]) HADOOP-9021. Enforce configured SASL method on the server (daryn via bobby) (Revision 1408473) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408473 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestSaslRPC.java Enforce configured SASL method on the server Key: HADOOP-9021 URL: https://issues.apache.org/jira/browse/HADOOP-9021 Project: Hadoop Common Issue Type: Sub-task Components: ipc, security Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0 Reporter: Daryn Sharp Assignee: Daryn Sharp Fix For: 3.0.0, 2.0.3-alpha Attachments: HADOOP-9021.patch, HADOOP-9021.patch The RPC needs to restrict itself to only using the configured SASL method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9022) Hadoop distcp tool fails to copy file if -m 0 specified
[ https://issues.apache.org/jira/browse/HADOOP-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496174#comment-13496174 ] Hudson commented on HADOOP-9022: Integrated in Hadoop-Hdfs-trunk #1225 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1225/]) HADOOP-9022. Hadoop distcp tool fails to copy file if -m 0 specified (Jonathan Eagles vai bobby) (Revision 1408488) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408488 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/DistCpOptions.java * /hadoop/common/trunk/hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/TestOptionsParser.java Hadoop distcp tool fails to copy file if -m 0 specified --- Key: HADOOP-9022 URL: https://issues.apache.org/jira/browse/HADOOP-9022 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.1, 0.23.3, 0.23.4 Reporter: Haiyang Jiang Assignee: Jonathan Eagles Fix For: 3.0.0, 2.0.3-alpha, 0.23.5 Attachments: HADOOP-9022.patch When trying to copy file using distcp on H23, if -m 0 is specified, distcp will just spawn 0 mapper tasks and the file will not be copied. But this used to work before H23, even when -m 0 specified, distcp will always copy the files. Checked the code of DistCp.java Before the rewrite, it set the number maps at least to 1 job.setNumMapTasks(Math.max(numMaps, 1)); But in the newest code, it just takes the input from user: job.getConfiguration().set(JobContext.NUM_MAPS, String.valueOf(inputOptions.getMaxMaps())); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9025) org.apache.hadoop.tools.TestCopyListing failing
[ https://issues.apache.org/jira/browse/HADOOP-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496180#comment-13496180 ] Hudson commented on HADOOP-9025: Integrated in Hadoop-Hdfs-trunk #1225 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1225/]) HADOOP-9025. org.apache.hadoop.tools.TestCopyListing failing. Contributed by Jonathan Eagles (Revision 1408604) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408604 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/TestCopyListing.java org.apache.hadoop.tools.TestCopyListing failing --- Key: HADOOP-9025 URL: https://issues.apache.org/jira/browse/HADOOP-9025 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0 Reporter: Robert Joseph Evans Assignee: Jonathan Eagles Fix For: 2.0.3-alpha, 0.23.5 Attachments: HADOOP-9025.patch https://builds.apache.org/job/PreCommit-HADOOP-Build/1732//testReport/org.apache.hadoop.tools/TestCopyListing/testDuplicates/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9025) org.apache.hadoop.tools.TestCopyListing failing
[ https://issues.apache.org/jira/browse/HADOOP-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496190#comment-13496190 ] tuvantlp.com commented on HADOOP-9025: -- http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói dịch vụ thành lập doanh nghiệp tư vấn thành lập doanh nghiệp http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html org.apache.hadoop.tools.TestCopyListing failing --- Key: HADOOP-9025 URL: https://issues.apache.org/jira/browse/HADOOP-9025 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0 Reporter: Robert Joseph Evans Assignee: Jonathan Eagles Fix For: 2.0.3-alpha, 0.23.5 Attachments: HADOOP-9025.patch https://builds.apache.org/job/PreCommit-HADOOP-Build/1732//testReport/org.apache.hadoop.tools/TestCopyListing/testDuplicates/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9025) org.apache.hadoop.tools.TestCopyListing failing
[ https://issues.apache.org/jira/browse/HADOOP-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496191#comment-13496191 ] tuvantlp.com commented on HADOOP-9025: -- http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/ http://tuvantlp.com/ http://tuvantlp.com/ http://tuvantlp.com/ thành lập doanh nghiệp; báo cáo thuế; sổ sách kế toán; dịch vụ kế toán org.apache.hadoop.tools.TestCopyListing failing --- Key: HADOOP-9025 URL: https://issues.apache.org/jira/browse/HADOOP-9025 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0 Reporter: Robert Joseph Evans Assignee: Jonathan Eagles Fix For: 2.0.3-alpha, 0.23.5 Attachments: HADOOP-9025.patch https://builds.apache.org/job/PreCommit-HADOOP-Build/1732//testReport/org.apache.hadoop.tools/TestCopyListing/testDuplicates/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9028) thành lập doanh nghiệp tuvantlp.com
tuvantlp.com created HADOOP-9028: Summary: thành lập doanh nghiệp tuvantlp.com Key: HADOOP-9028 URL: https://issues.apache.org/jira/browse/HADOOP-9028 Project: Hadoop Common Issue Type: Sub-task Components: benchmarks Affects Versions: 2.0.2-alpha Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Critical Fix For: hudson http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9029) tuvantlp.com
tuvantlp.com created HADOOP-9029: Summary: tuvantlp.com Key: HADOOP-9029 URL: https://issues.apache.org/jira/browse/HADOOP-9029 Project: Hadoop Common Issue Type: Sub-task Components: benchmarks Affects Versions: 2.0.2-alpha Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Minor Fix For: hudson http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9031) dịch vụ kế toán, thành lập doanh nghiệp, sổ sách kế toán
tuvantlp.com created HADOOP-9031: Summary: dịch vụ kế toán, thành lập doanh nghiệp, sổ sách kế toán Key: HADOOP-9031 URL: https://issues.apache.org/jira/browse/HADOOP-9031 Project: Hadoop Common Issue Type: Sub-task Components: benchmarks Affects Versions: 2.0.2-alpha Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Minor Fix For: hudson http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9030) thành lập doanh nghiệp, dịch vụ thành lập doanh nghiệp, tư vấn thành lập doanh nghiệp
tuvantlp.com created HADOOP-9030: Summary: thành lập doanh nghiệp, dịch vụ thành lập doanh nghiệp, tư vấn thành lập doanh nghiệp Key: HADOOP-9030 URL: https://issues.apache.org/jira/browse/HADOOP-9030 Project: Hadoop Common Issue Type: Sub-task Components: benchmarks Affects Versions: 2.0.2-alpha Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Minor Fix For: hudson http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9032) thanh lap doanh nghiep, báo cáo thuế, thành lập doanh nghiệp trọn gói
tuvantlp.com created HADOOP-9032: Summary: thanh lap doanh nghiep, báo cáo thuế, thành lập doanh nghiệp trọn gói Key: HADOOP-9032 URL: https://issues.apache.org/jira/browse/HADOOP-9032 Project: Hadoop Common Issue Type: Sub-task Components: benchmarks Affects Versions: 2.0.2-alpha Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Minor Fix For: hudson http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9033) thành lập doanh nghiệp hcm, dịch vụ kế toán, thành lập công ty, thanh lap doanh nghiep
tuvantlp.com created HADOOP-9033: Summary: thành lập doanh nghiệp hcm, dịch vụ kế toán, thành lập công ty, thanh lap doanh nghiep Key: HADOOP-9033 URL: https://issues.apache.org/jira/browse/HADOOP-9033 Project: Hadoop Common Issue Type: Sub-task Components: benchmarks Affects Versions: 2.0.2-alpha Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Minor Fix For: hudson http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9021) Enforce configured SASL method on the server
[ https://issues.apache.org/jira/browse/HADOOP-9021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496206#comment-13496206 ] Hudson commented on HADOOP-9021: Integrated in Hadoop-Mapreduce-trunk #1256 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1256/]) HADOOP-9021. Enforce configured SASL method on the server (daryn via bobby) (Revision 1408473) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408473 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestSaslRPC.java Enforce configured SASL method on the server Key: HADOOP-9021 URL: https://issues.apache.org/jira/browse/HADOOP-9021 Project: Hadoop Common Issue Type: Sub-task Components: ipc, security Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0 Reporter: Daryn Sharp Assignee: Daryn Sharp Fix For: 3.0.0, 2.0.3-alpha Attachments: HADOOP-9021.patch, HADOOP-9021.patch The RPC needs to restrict itself to only using the configured SASL method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8860) Split MapReduce and YARN sections in documentation navigation
[ https://issues.apache.org/jira/browse/HADOOP-8860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496205#comment-13496205 ] Hudson commented on HADOOP-8860: Integrated in Hadoop-Mapreduce-trunk #1256 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1256/]) Add new files missed from HADOOP-8860 commit. (Revision 1408288) Result = SUCCESS tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408288 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/resources * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/resources/css * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/site.xml * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/src/site/resources * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/src/site/resources/css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/resources * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/resources/css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/site.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/resources * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/resources/css * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/resources/css/site.css * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/site.xml Split MapReduce and YARN sections in documentation navigation - Key: HADOOP-8860 URL: https://issues.apache.org/jira/browse/HADOOP-8860 Project: Hadoop Common Issue Type: Task Components: documentation Affects Versions: 2.0.1-alpha Reporter: Tom White Assignee: Tom White Fix For: 2.0.3-alpha Attachments: HADOOP-8860-23.patch, HADOOP-8860-23.sh, HADOOP-8860.patch, HADOOP-8860.patch, HADOOP-8860.sh, HADOOP-8860.sh This JIRA is to change the navigation on http://hadoop.apache.org/docs/r2.0.1-alpha/ to reflect the fact that MapReduce and YARN are separate modules/sub-projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9022) Hadoop distcp tool fails to copy file if -m 0 specified
[ https://issues.apache.org/jira/browse/HADOOP-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496207#comment-13496207 ] Hudson commented on HADOOP-9022: Integrated in Hadoop-Mapreduce-trunk #1256 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1256/]) HADOOP-9022. Hadoop distcp tool fails to copy file if -m 0 specified (Jonathan Eagles vai bobby) (Revision 1408488) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408488 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/DistCpOptions.java * /hadoop/common/trunk/hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/TestOptionsParser.java Hadoop distcp tool fails to copy file if -m 0 specified --- Key: HADOOP-9022 URL: https://issues.apache.org/jira/browse/HADOOP-9022 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.1, 0.23.3, 0.23.4 Reporter: Haiyang Jiang Assignee: Jonathan Eagles Fix For: 3.0.0, 2.0.3-alpha, 0.23.5 Attachments: HADOOP-9022.patch When trying to copy file using distcp on H23, if -m 0 is specified, distcp will just spawn 0 mapper tasks and the file will not be copied. But this used to work before H23, even when -m 0 specified, distcp will always copy the files. Checked the code of DistCp.java Before the rewrite, it set the number maps at least to 1 job.setNumMapTasks(Math.max(numMaps, 1)); But in the newest code, it just takes the input from user: job.getConfiguration().set(JobContext.NUM_MAPS, String.valueOf(inputOptions.getMaxMaps())); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9025) org.apache.hadoop.tools.TestCopyListing failing
[ https://issues.apache.org/jira/browse/HADOOP-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496213#comment-13496213 ] Hudson commented on HADOOP-9025: Integrated in Hadoop-Mapreduce-trunk #1256 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1256/]) HADOOP-9025. org.apache.hadoop.tools.TestCopyListing failing. Contributed by Jonathan Eagles (Revision 1408604) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408604 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/TestCopyListing.java org.apache.hadoop.tools.TestCopyListing failing --- Key: HADOOP-9025 URL: https://issues.apache.org/jira/browse/HADOOP-9025 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0 Reporter: Robert Joseph Evans Assignee: Jonathan Eagles Fix For: 2.0.3-alpha, 0.23.5 Attachments: HADOOP-9025.patch https://builds.apache.org/job/PreCommit-HADOOP-Build/1732//testReport/org.apache.hadoop.tools/TestCopyListing/testDuplicates/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8999) SASL negotiation is flawed
[ https://issues.apache.org/jira/browse/HADOOP-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496232#comment-13496232 ] Daryn Sharp commented on HADOOP-8999: - I forgot to mention that tests are not included because the current ones are sufficient to prove this change does not break anything. When the PLAIN client is activated it will show that the change works. SASL negotiation is flawed -- Key: HADOOP-8999 URL: https://issues.apache.org/jira/browse/HADOOP-8999 Project: Hadoop Common Issue Type: Sub-task Components: ipc Reporter: Daryn Sharp Assignee: Daryn Sharp Attachments: HADOOP-8999.patch The RPC protocol used for SASL negotiation is flawed. The server's RPC response contains the next SASL challenge token, but a SASL server can return null (I'm done) or a N-many byte challenge. The server currently will not send a RPC success response to the client if the SASL server returns null, which causes the client to hang until it times out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8999) SASL negotiation is flawed
[ https://issues.apache.org/jira/browse/HADOOP-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496277#comment-13496277 ] Robert Joseph Evans commented on HADOOP-8999: - The change looks OK to me. So the problem is that the wrapper protocol around SASL that we have been using requires that the client not finish (aka isComplete() returns true) after a single challenge, and if it does we need to unconditionally read the response to possibly get the switch to SIMPLE message. Also that the server must reply at least once, again so that all clients both old and new will possibly get the switch to SIMPLE message. I don't like the special case you put into the server for PLAIN, but I don't see any other way around it without also changing the protocol version like you said previously. Daryn could you please file a separate JIRA to fix our SASL wrapper protocol so that we can send the success/failure/switch to SIMPLE message so that we can the plug in any java SASL client/server pair without needing to worry about special cases for them. I know that it would require a protocol version change but I think it is worth it. Perhaps not for 2.0, but definitely for a 3.0. +1 feel free to check it in. SASL negotiation is flawed -- Key: HADOOP-8999 URL: https://issues.apache.org/jira/browse/HADOOP-8999 Project: Hadoop Common Issue Type: Sub-task Components: ipc Reporter: Daryn Sharp Assignee: Daryn Sharp Attachments: HADOOP-8999.patch The RPC protocol used for SASL negotiation is flawed. The server's RPC response contains the next SASL challenge token, but a SASL server can return null (I'm done) or a N-many byte challenge. The server currently will not send a RPC success response to the client if the SASL server returns null, which causes the client to hang until it times out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9034) SASL negotiation is insufficient to support all types
Daryn Sharp created HADOOP-9034: --- Summary: SASL negotiation is insufficient to support all types Key: HADOOP-9034 URL: https://issues.apache.org/jira/browse/HADOOP-9034 Project: Hadoop Common Issue Type: Bug Components: ipc, security Affects Versions: 2.0.0-alpha, 0.23.0, 3.0.0 Reporter: Daryn Sharp A SASL negotiation requires a series of 1 or more challenge/responses. The current server-side RPC SASL implementation may respond with another challenge, an exception, or a switch to simple method. The server does not reply when the authentication handshake is complete. For SASL mechanisms that require multiple exchanges before the client believes the authentication is complete, the client has an opportunity to read the exception or switch to simple. However some mechanisms, ex. PLAIN, consider the exchange complete as soon as it sends the initial response. The following proxy call will read the SASL response and throw an incomplete protobuf exception. The same issue may manifest when a client sends the final response for a multi-exchange mechanism and the server returns an exception. Fixing the problem requires breaking RPC compatibility. We should consider having the SASL server always return success when authentication is complete. HADOOP-8999 added a short-term workaround to send a success response only for PLAIN, and for the client to always read at least one RPC response to ensure PLAIN will work. Another complication is a SASL server returns non-null when initiating another challenge and null when authentication is established. However, the current RPC exchange does not allow a zero-byte response (client, you initiate the exchange) to be differentiated from a null (client, we're authenticated!). We should consider using a different RPC status to indicate SASL authentication is in progress, so a zero-byte RPC success is interpreted as authentication is complete. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8999) SASL negotiation is flawed
[ https://issues.apache.org/jira/browse/HADOOP-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated HADOOP-8999: Resolution: Fixed Fix Version/s: 2.0.3-alpha 3.0.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for the review Bobby, I have committed to trunk and branch-2. SASL negotiation is flawed -- Key: HADOOP-8999 URL: https://issues.apache.org/jira/browse/HADOOP-8999 Project: Hadoop Common Issue Type: Sub-task Components: ipc Reporter: Daryn Sharp Assignee: Daryn Sharp Fix For: 3.0.0, 2.0.3-alpha Attachments: HADOOP-8999.patch The RPC protocol used for SASL negotiation is flawed. The server's RPC response contains the next SASL challenge token, but a SASL server can return null (I'm done) or a N-many byte challenge. The server currently will not send a RPC success response to the client if the SASL server returns null, which causes the client to hang until it times out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8999) SASL negotiation is flawed
[ https://issues.apache.org/jira/browse/HADOOP-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496339#comment-13496339 ] Hudson commented on HADOOP-8999: Integrated in Hadoop-trunk-Commit #3010 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3010/]) HADOOP-8999. SASL negotiation is flawed (daryn) (Revision 1408837) Result = SUCCESS daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1408837 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/SaslRpcClient.java SASL negotiation is flawed -- Key: HADOOP-8999 URL: https://issues.apache.org/jira/browse/HADOOP-8999 Project: Hadoop Common Issue Type: Sub-task Components: ipc Reporter: Daryn Sharp Assignee: Daryn Sharp Fix For: 3.0.0, 2.0.3-alpha Attachments: HADOOP-8999.patch The RPC protocol used for SASL negotiation is flawed. The server's RPC response contains the next SASL challenge token, but a SASL server can return null (I'm done) or a N-many byte challenge. The server currently will not send a RPC success response to the client if the SASL server returns null, which causes the client to hang until it times out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9027) Build fails on Windows without sh/sed/echo in the path
[ https://issues.apache.org/jira/browse/HADOOP-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496341#comment-13496341 ] Chris Nauroth commented on HADOOP-9027: --- Ivan, this looks good. In your testing on Ubuntu, did you also verify a build that bundles snappy? I have a VM ready with snappy installed if you want my help testing that. Can we delete fixFontsPath.sh and packageNativeHadoop.sh in this changeset? Build fails on Windows without sh/sed/echo in the path -- Key: HADOOP-9027 URL: https://issues.apache.org/jira/browse/HADOOP-9027 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9027.branch-1-win.cleanbuild.patch Branch-1-win still has a dependency on a few unix tools in compile time. Tracking Jira to remove this dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Deleted] (HADOOP-9028) thành lập doanh nghiệp tuvantlp.com
[ https://issues.apache.org/jira/browse/HADOOP-9028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon deleted HADOOP-9028: thành lập doanh nghiệp tuvantlp.com --- Key: HADOOP-9028 URL: https://issues.apache.org/jira/browse/HADOOP-9028 Project: Hadoop Common Issue Type: Sub-task Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Critical http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Deleted] (HADOOP-9033) thành lập doanh nghiệp hcm, dịch vụ kế toán, thành lập công ty, thanh lap doanh nghiep
[ https://issues.apache.org/jira/browse/HADOOP-9033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon deleted HADOOP-9033: thành lập doanh nghiệp hcm, dịch vụ kế toán, thành lập công ty, thanh lap doanh nghiep -- Key: HADOOP-9033 URL: https://issues.apache.org/jira/browse/HADOOP-9033 Project: Hadoop Common Issue Type: Sub-task Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Minor Labels: documentation http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Deleted] (HADOOP-9030) thành lập doanh nghiệp, dịch vụ thành lập doanh nghiệp, tư vấn thành lập doanh nghiệp
[ https://issues.apache.org/jira/browse/HADOOP-9030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon deleted HADOOP-9030: thành lập doanh nghiệp, dịch vụ thành lập doanh nghiệp, tư vấn thành lập doanh nghiệp - Key: HADOOP-9030 URL: https://issues.apache.org/jira/browse/HADOOP-9030 Project: Hadoop Common Issue Type: Sub-task Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Minor Labels: documentation http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Deleted] (HADOOP-9032) thanh lap doanh nghiep, báo cáo thuế, thành lập doanh nghiệp trọn gói
[ https://issues.apache.org/jira/browse/HADOOP-9032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon deleted HADOOP-9032: thanh lap doanh nghiep, báo cáo thuế, thành lập doanh nghiệp trọn gói - Key: HADOOP-9032 URL: https://issues.apache.org/jira/browse/HADOOP-9032 Project: Hadoop Common Issue Type: Sub-task Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Minor Labels: documentation http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Deleted] (HADOOP-9029) tuvantlp.com
[ https://issues.apache.org/jira/browse/HADOOP-9029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon deleted HADOOP-9029: tuvantlp.com Key: HADOOP-9029 URL: https://issues.apache.org/jira/browse/HADOOP-9029 Project: Hadoop Common Issue Type: Sub-task Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Minor Labels: documentation http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Deleted] (HADOOP-9031) dịch vụ kế toán, thành lập doanh nghiệp, sổ sách kế toán
[ https://issues.apache.org/jira/browse/HADOOP-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon deleted HADOOP-9031: dịch vụ kế toán, thành lập doanh nghiệp, sổ sách kế toán Key: HADOOP-9031 URL: https://issues.apache.org/jira/browse/HADOOP-9031 Project: Hadoop Common Issue Type: Sub-task Environment: http://tuvantlp.com/ thành lập doanh nghiệp thanh lap doanh nghiep Reporter: tuvantlp.com Priority: Minor Labels: documentation http://tuvantlp.com/ http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thành lập doanh nghiệp trọn gói thành lập doanh nghiệp giá rẻ tư vấn thành lập doanh nghiệp dịch vụ thành lập doanh nghiệp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7397) Allow configurable timeouts when connecting to HDFS via java FileSystem API
[ https://issues.apache.org/jira/browse/HADOOP-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-7397: Comment: was deleted (was: http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html http://tuvantlp.com/index.php/thanh-lap-doanh-nghiep.html thành lập doanh nghiệp thanh lap doanh nghiep thành lập doanh nghiệp trọn gói thành lập doanh nghiệp như thế nào dịch vụ kế toán sổ sách kế toán báo cáo thuế http://tuvantlp.com/index.php/dich-vu-ke-toan-thue.html http://tuvantlp.com/index.php/dich-vu-ke-toan-thue.html http://tuvantlp.com/index.php/dich-vu-ke-toan-thue.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html) Allow configurable timeouts when connecting to HDFS via java FileSystem API --- Key: HADOOP-7397 URL: https://issues.apache.org/jira/browse/HADOOP-7397 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 0.23.0 Reporter: Scott Fines Priority: Minor Labels: hadoop Attachments: HADOOP-7397.patch, timeout.patch If the NameNode is not available (in, for example, a network partition event separating the client from the NameNode), and an attempt is made to connect, then the FileSystem api will *eventually* timeout and throw an error. However, that timeout is currently hardcoded to be 20 seconds to connect, with 45 retries, for a total of a 15 minute wait before failure. While in many circumstances this is fine, there are also many circumstances (such as booting a service) where both the connection timeout and the number of retries should be significantly less, so as not to harm availability of other services. Investigating Client.java, I see that there are two fields in Connection: maxRetries and rpcTimeout. I propose either re-using those fields for initiating the connection as well; alternatively, using the already existing dfs.socket.timeout parameter to set the connection timeout on initialization, and potentially adding a new field such as dfs.connection.retries with a default of 45 to replicate current behaviors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7397) Allow configurable timeouts when connecting to HDFS via java FileSystem API
[ https://issues.apache.org/jira/browse/HADOOP-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-7397: Comment: was deleted (was: http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/index.php/bao-cao-thue-hang-thang.html http://tuvantlp.com/ http://tuvantlp.com/ http://tuvantlp.com/ http://tuvantlp.com/ http://tuvantlp.com/ Hướng dẫn thành lập doanh nghiệp Cần lưu ý những thông tin sau đây để tránh những sai sót rất dễ mắc phải khi soạn thảo hồ sơ thành lập doanh nghiệp: Xem bảng giá thành lập doanh nghiệp ở cuối bài này. 1. Chọn tên cho doanh nghiệp: (Khi thành lập doanh nghiệp phải chọn tên cho doanh nghiệp sao cho phù hợp với quy định và không được trùng tên, không gây nhầm lẫn với doanh nghiệp khác đã thành lập trước đó). Có thể kiểm tra tên doanh nghiệp ở Menu Nơi tra cứu thông tin: Dịch vụ thành lập doanh nghiệp, thành lập công ty. Những trường hợp sau đây được coi là gây nhầm lẫn với tên của các doanh nghiệp khác: a) Tên tiếng Việt, tên tiếng nước ngoài của doanh nghiệp dự định thành lập không được giống tên tiếng Việt, tên nước ngoài của doanh nghiệp khác đã thành lập trước đó. b) Tên của doanh nghiệp dự định thành lập chỉ khác tên của doanh nghiệp khác bởi ký hiệu ; ký hiệu - ; chữ và. c. Khi thành lập doanh nghiệp không đặt tên giống toàn bộ hay giống một phần của các cơ quan sau đây (trừ trường hợp có sự chấp thuận): Cơ quan nhà nước, Đơn vị lực lượng vũ trang nhân dân, Tên của tổ chức chính trị, tổ chức chính trị - xã hội. d. Không được sử dụng từ ngữ, ký hiệu vi phạm truyền thống lịch sử, văn hoá, đạo đức và thuần phong mỹ tục của dân tộc để đặt tên cho doanh nghiệp. e. Tên doanh nghiệp dự định thành lập không được giống tên thương mại của tổ chức, cá nhân khác đã đăng ký bảo hộ để cấu thành tên riêng của doanh nghiệp (trừ trường hợp được sự chấp thuận của chủ sở hữu). 2. Ngành, nghề kinh doanh của doanh nghiệp: (Trong giấy đề nghị đăng ký thành lập doanh nghiệp, yêu cầu ngành, nghề phải được mã hóa đến Cấp 4 theo Quyết định số 10/2007/QĐ-TTg ngày 23 tháng 01 năm 2007 của thủ Tướng Chính phủ). Sau khi thành lập, doanh nghiệp được quyền kinh doanh tất cả những ngành, nghề mà pháp luật không cấm. Nếu ngành, nghề kinh doanh yêu cầu có chứng chỉ hành nghề thì trong hồ sơ thành lập doanh nghiệp phải đính kèm chứng chỉ hành nghề sao y công chứng hoặc những giấy tờ cần thiết khác. Khi đăng ký thành lập doanh nghiệp cần lưu ý một số ngành, nghề yêu cầu phải có chứng chỉ hành nghề như: - Kinh doanh dịch vụ pháp lý. - Kinh doanh dịch vụ khám, chữa bệnh và kinh doanh dược phẩm. - Kinh doanh dịch vụ thú y, thuốc thú y. - Kinh doanh dịch vụ thiết kế quy hoạch xây dựng, khảo sát xây dựng, thiết kế xây dựng công trình, giám sát thi công xây dựng. - Kinh doanh dịch vụ kiểm toán. - Sản xuất, gia công, sang chai, đóng gói, mua bán thuốc bảo vệ thực vật. - Kinh doanh dịch vụ xông hơi khử trùng. - Kinh doanh dịch vụ thiết kế phương tiện vận tải. - Mua bán di vật, cổ vật, bảo vật quốc gia. - Kinh doanh dịch vụ kế toán. - Dịch vụ môi giới bất động sản, dịch vụ định giá bất động sản, dịch vụ sàn giao dịch bất động sản. Khi đăng ký thành lập doanh nghiệp cần lưu ý một số ngành, nghề yêu cầu phải có vốn pháp định như: (Vốn pháp định là số tiền tối thiểu bắt buộc phải có mới đủ điều kiện thành lập doanh nghiệp). - Tổ chức tín dụng, quỹ tín dụng nhân dân; tổ chức tín dụng phi ngân hàng. - Kinh doanh bất động sản. - Dịch vụ đòi nợ. - Dịch vụ đưa người lao động đi làm việc ở nước ngoài. - Sản xuất phim. - Cung cấp dịch vụ hàng không tại cảng hàng không. - Kinh doanh vận chuyển hàng không. - Kinh doanh vàng. Và một số ngành, nghề cấm kinh doanh: - Kinh doanh vũ khí quân dụng, trang thiết bị, kỹ thuật, khí tài, phương tiện chuyên dùng quân sự, công an. - Kinh doanh chất ma túy các loại. - Kinh doanh các sản phẩm văn hóa phản động, đồi trụy, mê tín dị đoan hoặc có hại tới giáo dục thẩm mỹ, nhân cách. - Kinh doanh các loại pháo. - Kinh doanh các loại đồ chơi, trò chơi nguy hiểm, đồ chơi, trò chơi có hại tới giáo dục nhân cách và sức khoẻ của trẻ em hoặc tới an ninh, trật tự an toàn xã hội. - Kinh doanh mại dâm, tổ chức mại dâm, buôn bán phụ nữ, trẻ em. - Kinh doanh dịch vụ tổ chức đánh bạc. - Kinh doanh dịch vụ điều tra bí mật xâm phạm lợi ích của Nhà nước, quyền và lợi ích hợp pháp của tổ chức, công dân. - Kinh doanh các loại phế liệu nhập khẩu gây ô nhiễm môi trường. - Kinh doanh các loại sản phẩm, hàng hoá và thiết bị cấm lưu hành, cấm sử dụng hoặc chưa được phép lưu hành/sử dụng tại Việt Nam. 3. Vốn điều lệ: + Vốn điều lệ là số vốn do các thành viên, cổ đông góp hoặc cam kết góp trong một thời hạn nhất định (được ghi rõ trong điều lệ của doanh nghiệp và giấy xin đăng ký thành lập doanh
[jira] [Commented] (HADOOP-9027) Build fails on Windows without sh/sed/echo in the path
[
https://issues.apache.org/jira/browse/HADOOP-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496368#comment-13496368
]
Ivan Mitic commented on HADOOP-9027:
Thanks for reviewing Chris!
bq. In your testing on Ubuntu, did you also verify a build that bundles snappy?
I have a VM ready with snappy installed if you want my help testing that.
I just verified that the files are binplaced properly and that permissions are
carried over. If you could test this on your VM that would be great!
bq. Can we delete fixFontsPath.sh and packageNativeHadoop.sh in this changeset?
I did not want to delete those since {{src\saveVersion.sh}} was also not
deleted in the branch. Will delete all 3 now.
Build fails on Windows without sh/sed/echo in the path
--
Key: HADOOP-9027
URL: https://issues.apache.org/jira/browse/HADOOP-9027
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 1-win
Reporter: Ivan Mitic
Assignee: Ivan Mitic
Attachments: HADOOP-9027.branch-1-win.cleanbuild.patch
Branch-1-win still has a dependency on a few unix tools in compile time.
Tracking Jira to remove this dependency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8999) SASL negotiation is flawed
[ https://issues.apache.org/jira/browse/HADOOP-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496386#comment-13496386 ] Devaraj Das commented on HADOOP-8999: - I haven't gone through the patch and what it solves but is this problem relevant to branch-1? SASL negotiation is flawed -- Key: HADOOP-8999 URL: https://issues.apache.org/jira/browse/HADOOP-8999 Project: Hadoop Common Issue Type: Sub-task Components: ipc Reporter: Daryn Sharp Assignee: Daryn Sharp Fix For: 3.0.0, 2.0.3-alpha Attachments: HADOOP-8999.patch The RPC protocol used for SASL negotiation is flawed. The server's RPC response contains the next SASL challenge token, but a SASL server can return null (I'm done) or a N-many byte challenge. The server currently will not send a RPC success response to the client if the SASL server returns null, which causes the client to hang until it times out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9024) Unit Test: TestKerberosAuthenticator fails when tested with ant-1.8.4
[
https://issues.apache.org/jira/browse/HADOOP-9024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amir Sanjar updated HADOOP-9024:
Attachment: HADOOP-9024-branch-1.patch
Unit Test: TestKerberosAuthenticator fails when tested with ant-1.8.4
--
Key: HADOOP-9024
URL: https://issues.apache.org/jira/browse/HADOOP-9024
Project: Hadoop Common
Issue Type: Bug
Components: test
Affects Versions: 1.0.3, 1.0.4
Environment: Linux Fedora 17_64
Reporter: Amir Sanjar
Priority: Minor
Fix For: 1.0.3, 1.0.4
Attachments: HADOOP-9024-branch-1.patch
Problem:
JUnit tag @Ignore is not recognized since the testcase is JUnit3 and not
JUnit4:
Solution:
Migrate the testcase to JUnit4
How:
Remove extends TestCase
SetUp and TearDown methods
@Override
protected void setUp() throws Exception { }
replaced by:
@Before
public void setUp() throws Exception { }
Same for tearDown():
@Override
protected void tearDown() throws Exception { }
replaced by
@After
public void tearDown() throws Exception { }
Imports
The imports has to be reorganized:
Remove import junit.framework.TestCase;
Add org.junit.*; or import org.junit.After; import org.junit.Before;
import org.junit.Test;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9024) Unit Test: TestKerberosAuthenticator fails when tested with ant-1.8.4
[
https://issues.apache.org/jira/browse/HADOOP-9024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amir Sanjar updated HADOOP-9024:
Status: Patch Available (was: Open)
Unit Test: TestKerberosAuthenticator fails when tested with ant-1.8.4
--
Key: HADOOP-9024
URL: https://issues.apache.org/jira/browse/HADOOP-9024
Project: Hadoop Common
Issue Type: Bug
Components: test
Affects Versions: 1.0.4, 1.0.3
Environment: Linux Fedora 17_64
Reporter: Amir Sanjar
Priority: Minor
Fix For: 1.0.4, 1.0.3
Attachments: HADOOP-9024-branch-1.patch
Problem:
JUnit tag @Ignore is not recognized since the testcase is JUnit3 and not
JUnit4:
Solution:
Migrate the testcase to JUnit4
How:
Remove extends TestCase
SetUp and TearDown methods
@Override
protected void setUp() throws Exception { }
replaced by:
@Before
public void setUp() throws Exception { }
Same for tearDown():
@Override
protected void tearDown() throws Exception { }
replaced by
@After
public void tearDown() throws Exception { }
Imports
The imports has to be reorganized:
Remove import junit.framework.TestCase;
Add org.junit.*; or import org.junit.After; import org.junit.Before;
import org.junit.Test;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8999) SASL negotiation is flawed
[ https://issues.apache.org/jira/browse/HADOOP-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496438#comment-13496438 ] Daryn Sharp commented on HADOOP-8999: - The general problem is present in branch-1, but won't be exposed unless other SASL methods are added to branch-1. SASL negotiation is flawed -- Key: HADOOP-8999 URL: https://issues.apache.org/jira/browse/HADOOP-8999 Project: Hadoop Common Issue Type: Sub-task Components: ipc Reporter: Daryn Sharp Assignee: Daryn Sharp Fix For: 3.0.0, 2.0.3-alpha Attachments: HADOOP-8999.patch The RPC protocol used for SASL negotiation is flawed. The server's RPC response contains the next SASL challenge token, but a SASL server can return null (I'm done) or a N-many byte challenge. The server currently will not send a RPC success response to the client if the SASL server returns null, which causes the client to hang until it times out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8820) Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup)
[ https://issues.apache.org/jira/browse/HADOOP-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496481#comment-13496481 ] Tsz Wo (Nicholas), SZE commented on HADOOP-8820: Junping, there is no easy way to review such a big patch in HADOOP-8817. It is simply too big. Also, branch-1 is a stable branch so that we must be conservative. Splitting it into 4 parts HADOOP-8820, HDFS-3941, HDFS-3942 and MAPREDUCE-4660 sounds really good. Would you mind doing it? In the meantime, I will review your balancer patch for trunk. Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup) --- Key: HADOOP-8820 URL: https://issues.apache.org/jira/browse/HADOOP-8820 Project: Hadoop Common Issue Type: New Feature Components: net Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-8820.b1.002.patch, HADOOP-8820.b1.003.patch, HADOOP-8820.patch This patch backport HADOOP-8469 and HADOOP-8470 to branch-1 and includes: 1. Make NetworkTopology class pluggable for extension. 2. Implement a 4-layer NetworkTopology class (named as NetworkTopologyWithNodeGroup) to use in virtualized environment (or other situation with additional layer between host and rack). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8820) Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup)
[ https://issues.apache.org/jira/browse/HADOOP-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496506#comment-13496506 ] Junping Du commented on HADOOP-8820: Ok. Sounds good. I will split the patch into 4 patches. Thanks. Nicholas! Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup) --- Key: HADOOP-8820 URL: https://issues.apache.org/jira/browse/HADOOP-8820 Project: Hadoop Common Issue Type: New Feature Components: net Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-8820.b1.002.patch, HADOOP-8820.b1.003.patch, HADOOP-8820.patch This patch backport HADOOP-8469 and HADOOP-8470 to branch-1 and includes: 1. Make NetworkTopology class pluggable for extension. 2. Implement a 4-layer NetworkTopology class (named as NetworkTopologyWithNodeGroup) to use in virtualized environment (or other situation with additional layer between host and rack). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-7411) Convert remaining Ant based build to Maven
[ https://issues.apache.org/jira/browse/HADOOP-7411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur resolved HADOOP-7411. Resolution: Duplicate MAPREDUCE-4266 took care of removing the ant stuff which was not used anymore Convert remaining Ant based build to Maven -- Key: HADOOP-7411 URL: https://issues.apache.org/jira/browse/HADOOP-7411 Project: Hadoop Common Issue Type: Sub-task Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Once Mavenization is complete, do a second iteration to remove antrun calls out, this may require writing some Mojos. The tricky things are native compilation and symlinks handling (for native libs) when creating packaging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8820) Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup)
[ https://issues.apache.org/jira/browse/HADOOP-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496532#comment-13496532 ] Tsz Wo (Nicholas), SZE commented on HADOOP-8820: That's great. Thanks, Junping. Then, I will first commit HADOOP-8820.b1.002.patch. For the additional bug fixes, let's create a new JIRA since we also need to fix the code in trunk. Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup) --- Key: HADOOP-8820 URL: https://issues.apache.org/jira/browse/HADOOP-8820 Project: Hadoop Common Issue Type: New Feature Components: net Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-8820.b1.002.patch, HADOOP-8820.b1.003.patch, HADOOP-8820.patch This patch backport HADOOP-8469 and HADOOP-8470 to branch-1 and includes: 1. Make NetworkTopology class pluggable for extension. 2. Implement a 4-layer NetworkTopology class (named as NetworkTopologyWithNodeGroup) to use in virtualized environment (or other situation with additional layer between host and rack). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8820) Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup)
[ https://issues.apache.org/jira/browse/HADOOP-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496539#comment-13496539 ] Jing Zhao commented on HADOOP-8820: --- By the way, I've run unit tests locally for both 002 and 003 patches, and all the tests passed except TestFileCreation, which should be unrelated and has been reported in HDFS-4180. Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup) --- Key: HADOOP-8820 URL: https://issues.apache.org/jira/browse/HADOOP-8820 Project: Hadoop Common Issue Type: New Feature Components: net Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-8820.b1.002.patch, HADOOP-8820.b1.003.patch, HADOOP-8820.patch This patch backport HADOOP-8469 and HADOOP-8470 to branch-1 and includes: 1. Make NetworkTopology class pluggable for extension. 2. Implement a 4-layer NetworkTopology class (named as NetworkTopologyWithNodeGroup) to use in virtualized environment (or other situation with additional layer between host and rack). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9011) saveVersion.py does not include branch in version annotation
[ https://issues.apache.org/jira/browse/HADOOP-9011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496561#comment-13496561 ] Raja Aluri commented on HADOOP-9011: +1 LGTM saveVersion.py does not include branch in version annotation Key: HADOOP-9011 URL: https://issues.apache.org/jira/browse/HADOOP-9011 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: trunk-win Reporter: Chris Nauroth Assignee: Chris Nauroth Attachments: HADOOP-9011-branch-trunk-win.patch HADOOP-8924 created saveVersion.py on branch-trunk-win. Unlike saveVersion.sh on trunk, it did not include the branch attribute in the version annotation. This causes errors at runtime for anything that tries to read the annotation via VersionInfo. This also causes a unit test failure in TestYarnVersionInfo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8820) Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup)
[ https://issues.apache.org/jira/browse/HADOOP-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496570#comment-13496570 ] Junping Du commented on HADOOP-8820: Great. Thanks Nicholas! Also, Thanks Jing for review and verification. Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup) --- Key: HADOOP-8820 URL: https://issues.apache.org/jira/browse/HADOOP-8820 Project: Hadoop Common Issue Type: New Feature Components: net Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-8820.b1.002.patch, HADOOP-8820.b1.003.patch, HADOOP-8820.patch This patch backport HADOOP-8469 and HADOOP-8470 to branch-1 and includes: 1. Make NetworkTopology class pluggable for extension. 2. Implement a 4-layer NetworkTopology class (named as NetworkTopologyWithNodeGroup) to use in virtualized environment (or other situation with additional layer between host and rack). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8820) Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup)
[ https://issues.apache.org/jira/browse/HADOOP-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HADOOP-8820. Resolution: Fixed Fix Version/s: 1-win 1.2.0 Hadoop Flags: Reviewed +1 on HADOOP-8820.b1.002.patch I have committed it. Thanks, Junping and Jing! Backport HADOOP-8469 and HADOOP-8470: add NodeGroup layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup) --- Key: HADOOP-8820 URL: https://issues.apache.org/jira/browse/HADOOP-8820 Project: Hadoop Common Issue Type: New Feature Components: net Affects Versions: 1.0.0 Reporter: Junping Du Assignee: Junping Du Fix For: 1.2.0, 1-win Attachments: HADOOP-8820.b1.002.patch, HADOOP-8820.b1.003.patch, HADOOP-8820.patch This patch backport HADOOP-8469 and HADOOP-8470 to branch-1 and includes: 1. Make NetworkTopology class pluggable for extension. 2. Implement a 4-layer NetworkTopology class (named as NetworkTopologyWithNodeGroup) to use in virtualized environment (or other situation with additional layer between host and rack). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9035) Generalize setup of LoginContext
Daryn Sharp created HADOOP-9035:
---
Summary: Generalize setup of LoginContext
Key: HADOOP-9035
URL: https://issues.apache.org/jira/browse/HADOOP-9035
Project: Hadoop Common
Issue Type: Sub-task
Components: security
Affects Versions: 2.0.0-alpha, 0.23.0, 3.0.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
The creation of the {{LoginContext}} in {{UserGroupInformation}} has specific
cases for specific authentication types. This is inflexible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9035) Generalize setup of LoginContext
[
https://issues.apache.org/jira/browse/HADOOP-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-9035:
Attachment: HADOOP-9035.patch
Associate the login config name with the {{AuthenticationMethod}}, then remove
switches and use the login config based on the configured auth method.
Generalize setup of LoginContext
Key: HADOOP-9035
URL: https://issues.apache.org/jira/browse/HADOOP-9035
Project: Hadoop Common
Issue Type: Sub-task
Components: security
Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-9035.patch
The creation of the {{LoginContext}} in {{UserGroupInformation}} has specific
cases for specific authentication types. This is inflexible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9035) Generalize setup of LoginContext
[
https://issues.apache.org/jira/browse/HADOOP-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-9035:
Status: Patch Available (was: Open)
Generalize setup of LoginContext
Key: HADOOP-9035
URL: https://issues.apache.org/jira/browse/HADOOP-9035
Project: Hadoop Common
Issue Type: Sub-task
Components: security
Affects Versions: 2.0.0-alpha, 0.23.0, 3.0.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-9035.patch
The creation of the {{LoginContext}} in {{UserGroupInformation}} has specific
cases for specific authentication types. This is inflexible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9035) Generalize setup of LoginContext
[
https://issues.apache.org/jira/browse/HADOOP-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-9035:
Status: Open (was: Patch Available)
Bad patch.
Generalize setup of LoginContext
Key: HADOOP-9035
URL: https://issues.apache.org/jira/browse/HADOOP-9035
Project: Hadoop Common
Issue Type: Sub-task
Components: security
Affects Versions: 2.0.0-alpha, 0.23.0, 3.0.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-9035.patch
The creation of the {{LoginContext}} in {{UserGroupInformation}} has specific
cases for specific authentication types. This is inflexible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-9011) saveVersion.py does not include branch in version annotation
[ https://issues.apache.org/jira/browse/HADOOP-9011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HADOOP-9011. - Resolution: Fixed Fix Version/s: trunk-win Hadoop Flags: Reviewed +1. Committed to branch-trunk-win. Thank you Chris. Thank you Raja for the review. saveVersion.py does not include branch in version annotation Key: HADOOP-9011 URL: https://issues.apache.org/jira/browse/HADOOP-9011 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: trunk-win Reporter: Chris Nauroth Assignee: Chris Nauroth Fix For: trunk-win Attachments: HADOOP-9011-branch-trunk-win.patch HADOOP-8924 created saveVersion.py on branch-trunk-win. Unlike saveVersion.sh on trunk, it did not include the branch attribute in the version annotation. This causes errors at runtime for anything that tries to read the annotation via VersionInfo. This also causes a unit test failure in TestYarnVersionInfo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8943) Enable to support multiple ADs and different group mapping for different user
[ https://issues.apache.org/jira/browse/HADOOP-8943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Zheng updated HADOOP-8943: -- Attachment: HADOOP-8943.patch Initial patch for review. Enable to support multiple ADs and different group mapping for different user - Key: HADOOP-8943 URL: https://issues.apache.org/jira/browse/HADOOP-8943 Project: Hadoop Common Issue Type: Improvement Components: security Reporter: Kai Zheng Fix For: 2.0.3-alpha Attachments: HADOOP-8943.patch Original Estimate: 504h Remaining Estimate: 504h Discussed with Natty about LdapGroupMapping, we need to improve it so that: 1. It's possible to do different group mapping for different users/principals. For example, AD user should go to LdapGroupMapping service for group, but service principals such as hdfs, mapred can still use the default one ShellBasedUnixGroupsMapping; 2. Multiple ADs can be supported to do LdapGroupMapping; 3. It's possible to configure what kind of users/principals (regarding domain/realm is an option) should use which group mapping service/mechanism. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8998) send Cache-Control header on JSP pages
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-8998:
---
Attachment: HADOOP-8998.patch
adding a filter that is used for everything except static/ that sets
'Cache-Control: no-cache' header
send Cache-Control header on JSP pages
--
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Attachments: HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8998) send Cache-Control header on JSP pages
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-8998:
---
Status: Patch Available (was: Open)
send Cache-Control header on JSP pages
--
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Attachments: HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9034) SASL negotiation is insufficient to support all types
[ https://issues.apache.org/jira/browse/HADOOP-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496724#comment-13496724 ] Kan Zhang commented on HADOOP-9034: --- bq. We should consider having the SASL server always return success when authentication is complete. ..., and for the client to always read at least one RPC response to ensure PLAIN will work. Sounds good to me. SASL negotiation is insufficient to support all types - Key: HADOOP-9034 URL: https://issues.apache.org/jira/browse/HADOOP-9034 Project: Hadoop Common Issue Type: Bug Components: ipc, security Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0 Reporter: Daryn Sharp A SASL negotiation requires a series of 1 or more challenge/responses. The current server-side RPC SASL implementation may respond with another challenge, an exception, or a switch to simple method. The server does not reply when the authentication handshake is complete. For SASL mechanisms that require multiple exchanges before the client believes the authentication is complete, the client has an opportunity to read the exception or switch to simple. However some mechanisms, ex. PLAIN, consider the exchange complete as soon as it sends the initial response. The following proxy call will read the SASL response and throw an incomplete protobuf exception. The same issue may manifest when a client sends the final response for a multi-exchange mechanism and the server returns an exception. Fixing the problem requires breaking RPC compatibility. We should consider having the SASL server always return success when authentication is complete. HADOOP-8999 added a short-term workaround to send a success response only for PLAIN, and for the client to always read at least one RPC response to ensure PLAIN will work. Another complication is a SASL server returns non-null when initiating another challenge and null when authentication is established. However, the current RPC exchange does not allow a zero-byte response (client, you initiate the exchange) to be differentiated from a null (client, we're authenticated!). We should consider using a different RPC status to indicate SASL authentication is in progress, so a zero-byte RPC success is interpreted as authentication is complete. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9036) TestSinkQueue.testConcurrentConsumers fails
Ivan Mitic created HADOOP-9036: -- Summary: TestSinkQueue.testConcurrentConsumers fails Key: HADOOP-9036 URL: https://issues.apache.org/jira/browse/HADOOP-9036 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers Error Message should've thrown Stacktrace junit.framework.AssertionFailedError: should've thrown at org.apache.hadoop.metrics2.impl.TestSinkQueue.shouldThrowCME(TestSinkQueue.java:229) at org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers(TestSinkQueue.java:195) Standard Output 2012-10-03 16:51:31,694 INFO impl.TestSinkQueue (TestSinkQueue.java:consume(243)) - sleeping -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9036) TestSinkQueue.testConcurrentConsumers fails
[ https://issues.apache.org/jira/browse/HADOOP-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496743#comment-13496743 ] Ivan Mitic commented on HADOOP-9036: There is a race condition in TestSinkQueue#testConcurrentConsumers between a new thread created in newSleepingConsumerQueue and the first assert shouldThrowCME, hence the test fails intermittently. Each time shouldThrowCME runs before the new thread receives a consume callback the test will fail. The easiest way to consistently repro the problem is to add a short Thread.sleep in the newSleepingConsumerQueue thread. TestSinkQueue.testConcurrentConsumers fails --- Key: HADOOP-9036 URL: https://issues.apache.org/jira/browse/HADOOP-9036 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers Error Message should've thrown Stacktrace junit.framework.AssertionFailedError: should've thrown at org.apache.hadoop.metrics2.impl.TestSinkQueue.shouldThrowCME(TestSinkQueue.java:229) at org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers(TestSinkQueue.java:195) Standard Output 2012-10-03 16:51:31,694 INFO impl.TestSinkQueue (TestSinkQueue.java:consume(243)) - sleeping -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9036) TestSinkQueue.testConcurrentConsumers fails
[ https://issues.apache.org/jira/browse/HADOOP-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Mitic updated HADOOP-9036: --- Attachment: HADOOP-9036.branch-1-win.testsinkqueue.patch Attaching the patch. TestSinkQueue.testConcurrentConsumers fails --- Key: HADOOP-9036 URL: https://issues.apache.org/jira/browse/HADOOP-9036 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9036.branch-1-win.testsinkqueue.patch org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers Error Message should've thrown Stacktrace junit.framework.AssertionFailedError: should've thrown at org.apache.hadoop.metrics2.impl.TestSinkQueue.shouldThrowCME(TestSinkQueue.java:229) at org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers(TestSinkQueue.java:195) Standard Output 2012-10-03 16:51:31,694 INFO impl.TestSinkQueue (TestSinkQueue.java:consume(243)) - sleeping -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9036) TestSinkQueue.testConcurrentConsumers fails
[ https://issues.apache.org/jira/browse/HADOOP-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Mitic updated HADOOP-9036: --- Status: Patch Available (was: Open) TestSinkQueue.testConcurrentConsumers fails --- Key: HADOOP-9036 URL: https://issues.apache.org/jira/browse/HADOOP-9036 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9036.branch-1-win.testsinkqueue.patch org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers Error Message should've thrown Stacktrace junit.framework.AssertionFailedError: should've thrown at org.apache.hadoop.metrics2.impl.TestSinkQueue.shouldThrowCME(TestSinkQueue.java:229) at org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers(TestSinkQueue.java:195) Standard Output 2012-10-03 16:51:31,694 INFO impl.TestSinkQueue (TestSinkQueue.java:consume(243)) - sleeping -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9036) TestSinkQueue.testConcurrentConsumers fails
[
https://issues.apache.org/jira/browse/HADOOP-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496756#comment-13496756
]
Hadoop QA commented on HADOOP-9036:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553425/HADOOP-9036.branch-1-win.testsinkqueue.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1737//console
This message is automatically generated.
TestSinkQueue.testConcurrentConsumers fails
---
Key: HADOOP-9036
URL: https://issues.apache.org/jira/browse/HADOOP-9036
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 1-win
Reporter: Ivan Mitic
Assignee: Ivan Mitic
Attachments: HADOOP-9036.branch-1-win.testsinkqueue.patch
org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers
Error Message
should've thrown
Stacktrace
junit.framework.AssertionFailedError: should've thrown
at
org.apache.hadoop.metrics2.impl.TestSinkQueue.shouldThrowCME(TestSinkQueue.java:229)
at
org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers(TestSinkQueue.java:195)
Standard Output
2012-10-03 16:51:31,694 INFO impl.TestSinkQueue
(TestSinkQueue.java:consume(243)) - sleeping
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8972) Move winutils tests from bat to Java
[ https://issues.apache.org/jira/browse/HADOOP-8972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496759#comment-13496759 ] Ivan Mitic commented on HADOOP-8972: Suresh, should we resolve this Jira? Move winutils tests from bat to Java Key: HADOOP-8972 URL: https://issues.apache.org/jira/browse/HADOOP-8972 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Fix For: 1-win Attachments: HADOOP-8972.branch-1-win.update.deletefiles.patch, HADOOP-8972.branch-1-win.winutilstests.patch This Jira tracks the work needed to move existing winutils tests from bat files to Java. We decided to go with Java for the following reasons: 1. It showed to be quite hard to modify bat scripts and add new test cases (people are generally not comfortable writing bat scripts) 2. Debugging a test case failure in bat script is not trivial 3. It turned that we are not running the test scripts frequently Cons: One now needs JDK and Hadoop jar to compile and run winutils tests. However, in the context of Hadoop this is not an issue so we decided to go with something we all feel more comfortable with. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9027) Build fails on Windows without sh/sed/echo in the path
[ https://issues.apache.org/jira/browse/HADOOP-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Mitic updated HADOOP-9027: --- Attachment: HADOOP-9027.branch-1-win.cleanbuild.2.patch Attaching updated patch where I deleted the no longer needed files. Build fails on Windows without sh/sed/echo in the path -- Key: HADOOP-9027 URL: https://issues.apache.org/jira/browse/HADOOP-9027 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9027.branch-1-win.cleanbuild.2.patch, HADOOP-9027.branch-1-win.cleanbuild.patch Branch-1-win still has a dependency on a few unix tools in compile time. Tracking Jira to remove this dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9036) TestSinkQueue.testConcurrentConsumers fails
[ https://issues.apache.org/jira/browse/HADOOP-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496765#comment-13496765 ] Chuan Liu commented on HADOOP-9036: --- +1 Is 0.1 second enough? TestSinkQueue.testConcurrentConsumers fails --- Key: HADOOP-9036 URL: https://issues.apache.org/jira/browse/HADOOP-9036 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9036.branch-1-win.testsinkqueue.patch org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers Error Message should've thrown Stacktrace junit.framework.AssertionFailedError: should've thrown at org.apache.hadoop.metrics2.impl.TestSinkQueue.shouldThrowCME(TestSinkQueue.java:229) at org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers(TestSinkQueue.java:195) Standard Output 2012-10-03 16:51:31,694 INFO impl.TestSinkQueue (TestSinkQueue.java:consume(243)) - sleeping -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9026) Hadoop.cmd fails to initialize if user's %path% variable has parenthesis
[ https://issues.apache.org/jira/browse/HADOOP-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496770#comment-13496770 ] Chuan Liu commented on HADOOP-9026: --- Do we still need to remove '(x86)' in path after this change? Hadoop.cmd fails to initialize if user's %path% variable has parenthesis Key: HADOOP-9026 URL: https://issues.apache.org/jira/browse/HADOOP-9026 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9026.branch-1-win.pathfix.patch Hadoop.cmd fails to initialize if user's %path% variable has parenthesis. This happens in updatepath module while tring the add Hadoop_bin_path to %path% Repro: 1. Create a folder C:\random() 2. Add this path to %path% 3. Start Hadoop command line Error: path_after_c:\rand(); unexpected at this time Reported by Ramya Nimmagadda. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8998) send Cache-Control header on JSP pages
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496773#comment-13496773
]
Hadoop QA commented on HADOOP-8998:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553412/HADOOP-8998.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1738//console
This message is automatically generated.
send Cache-Control header on JSP pages
--
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Attachments: HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9036) TestSinkQueue.testConcurrentConsumers fails
[ https://issues.apache.org/jira/browse/HADOOP-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496776#comment-13496776 ] Ivan Mitic commented on HADOOP-9036: bq. Is 0.1 second enough? Thanks for reviewing Chuan. It should be enough. TestSinkQueue.testConcurrentConsumers fails --- Key: HADOOP-9036 URL: https://issues.apache.org/jira/browse/HADOOP-9036 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9036.branch-1-win.testsinkqueue.patch org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers Error Message should've thrown Stacktrace junit.framework.AssertionFailedError: should've thrown at org.apache.hadoop.metrics2.impl.TestSinkQueue.shouldThrowCME(TestSinkQueue.java:229) at org.apache.hadoop.metrics2.impl.TestSinkQueue.testConcurrentConsumers(TestSinkQueue.java:195) Standard Output 2012-10-03 16:51:31,694 INFO impl.TestSinkQueue (TestSinkQueue.java:consume(243)) - sleeping -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9026) Hadoop.cmd fails to initialize if user's %path% variable has parenthesis
[ https://issues.apache.org/jira/browse/HADOOP-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496778#comment-13496778 ] Ivan Mitic commented on HADOOP-9026: bq. Do we still need to remove '(x86)' in path after this change? Good question Chuan. I actually think that we do not. I'll update the patch. Hadoop.cmd fails to initialize if user's %path% variable has parenthesis Key: HADOOP-9026 URL: https://issues.apache.org/jira/browse/HADOOP-9026 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9026.branch-1-win.pathfix.patch Hadoop.cmd fails to initialize if user's %path% variable has parenthesis. This happens in updatepath module while tring the add Hadoop_bin_path to %path% Repro: 1. Create a folder C:\random() 2. Add this path to %path% 3. Start Hadoop command line Error: path_after_c:\rand(); unexpected at this time Reported by Ramya Nimmagadda. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9026) Hadoop.cmd fails to initialize if user's %path% variable has parenthesis
[ https://issues.apache.org/jira/browse/HADOOP-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Mitic updated HADOOP-9026: --- Attachment: HADOOP-9026.branch-1-win.pathfix.2.patch Attaching updated patch. Hadoop.cmd fails to initialize if user's %path% variable has parenthesis Key: HADOOP-9026 URL: https://issues.apache.org/jira/browse/HADOOP-9026 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9026.branch-1-win.pathfix.2.patch, HADOOP-9026.branch-1-win.pathfix.patch Hadoop.cmd fails to initialize if user's %path% variable has parenthesis. This happens in updatepath module while tring the add Hadoop_bin_path to %path% Repro: 1. Create a folder C:\random() 2. Add this path to %path% 3. Start Hadoop command line Error: path_after_c:\rand(); unexpected at this time Reported by Ramya Nimmagadda. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9026) Hadoop.cmd fails to initialize if user's %path% variable has parenthesis
[ https://issues.apache.org/jira/browse/HADOOP-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496792#comment-13496792 ] Chuan Liu commented on HADOOP-9026: --- +1 Thanks for the fix! Hadoop.cmd fails to initialize if user's %path% variable has parenthesis Key: HADOOP-9026 URL: https://issues.apache.org/jira/browse/HADOOP-9026 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9026.branch-1-win.pathfix.2.patch, HADOOP-9026.branch-1-win.pathfix.patch Hadoop.cmd fails to initialize if user's %path% variable has parenthesis. This happens in updatepath module while tring the add Hadoop_bin_path to %path% Repro: 1. Create a folder C:\random() 2. Add this path to %path% 3. Start Hadoop command line Error: path_after_c:\rand(); unexpected at this time Reported by Ramya Nimmagadda. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8972) Move winutils tests from bat to Java
[ https://issues.apache.org/jira/browse/HADOOP-8972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HADOOP-8972. - Resolution: Fixed Done Move winutils tests from bat to Java Key: HADOOP-8972 URL: https://issues.apache.org/jira/browse/HADOOP-8972 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Fix For: 1-win Attachments: HADOOP-8972.branch-1-win.update.deletefiles.patch, HADOOP-8972.branch-1-win.winutilstests.patch This Jira tracks the work needed to move existing winutils tests from bat files to Java. We decided to go with Java for the following reasons: 1. It showed to be quite hard to modify bat scripts and add new test cases (people are generally not comfortable writing bat scripts) 2. Debugging a test case failure in bat script is not trivial 3. It turned that we are not running the test scripts frequently Cons: One now needs JDK and Hadoop jar to compile and run winutils tests. However, in the context of Hadoop this is not an issue so we decided to go with something we all feel more comfortable with. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8972) Move winutils tests from bat to Java
[ https://issues.apache.org/jira/browse/HADOOP-8972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496801#comment-13496801 ] Ivan Mitic commented on HADOOP-8972: Thanks, wasn't sure if there is something else needed besides resolving the Jira :) Move winutils tests from bat to Java Key: HADOOP-8972 URL: https://issues.apache.org/jira/browse/HADOOP-8972 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Fix For: 1-win Attachments: HADOOP-8972.branch-1-win.update.deletefiles.patch, HADOOP-8972.branch-1-win.winutilstests.patch This Jira tracks the work needed to move existing winutils tests from bat files to Java. We decided to go with Java for the following reasons: 1. It showed to be quite hard to modify bat scripts and add new test cases (people are generally not comfortable writing bat scripts) 2. Debugging a test case failure in bat script is not trivial 3. It turned that we are not running the test scripts frequently Cons: One now needs JDK and Hadoop jar to compile and run winutils tests. However, in the context of Hadoop this is not an issue so we decided to go with something we all feel more comfortable with. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8998) send Cache-Control header on JSP pages
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-8998:
---
Attachment: HADOOP-8998.patch
send Cache-Control header on JSP pages
--
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Attachments: HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8998) send Cache-Control header on JSP pages
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-8998:
---
Attachment: (was: HADOOP-8998.patch)
send Cache-Control header on JSP pages
--
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Attachments: HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9026) Hadoop.cmd fails to initialize if user's %path% variable has parenthesis
[
https://issues.apache.org/jira/browse/HADOOP-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496827#comment-13496827
]
Hadoop QA commented on HADOOP-9026:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553435/HADOOP-9026.branch-1-win.pathfix.2.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1739//console
This message is automatically generated.
Hadoop.cmd fails to initialize if user's %path% variable has parenthesis
Key: HADOOP-9026
URL: https://issues.apache.org/jira/browse/HADOOP-9026
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 1-win
Reporter: Ivan Mitic
Assignee: Ivan Mitic
Attachments: HADOOP-9026.branch-1-win.pathfix.2.patch,
HADOOP-9026.branch-1-win.pathfix.patch
Hadoop.cmd fails to initialize if user's %path% variable has parenthesis.
This happens in updatepath module while tring the add Hadoop_bin_path to
%path%
Repro:
1. Create a folder C:\random()
2. Add this path to %path%
3. Start Hadoop command line
Error:
path_after_c:\rand(); unexpected at this time
Reported by Ramya Nimmagadda.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9026) Hadoop.cmd fails to initialize if user's %path% variable has parenthesis
[ https://issues.apache.org/jira/browse/HADOOP-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496829#comment-13496829 ] Chuan Liu commented on HADOOP-9026: --- Hello, I am traveling and can only check my emails sporadically. I will respond to your message on or after Nov 23, 2012 (if not sooner). Thanks. Hadoop.cmd fails to initialize if user's %path% variable has parenthesis Key: HADOOP-9026 URL: https://issues.apache.org/jira/browse/HADOOP-9026 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9026.branch-1-win.pathfix.2.patch, HADOOP-9026.branch-1-win.pathfix.patch Hadoop.cmd fails to initialize if user's %path% variable has parenthesis. This happens in updatepath module while tring the add Hadoop_bin_path to %path% Repro: 1. Create a folder C:\random() 2. Add this path to %path% 3. Start Hadoop command line Error: path_after_c:\rand(); unexpected at this time Reported by Ramya Nimmagadda. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8998) send Cache-Control header on JSP pages
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496853#comment-13496853
]
Hadoop QA commented on HADOOP-8998:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553441/HADOOP-8998.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 2029 javac
compiler warnings (more than the trunk's current 2028 warnings).
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1740//testReport/
Javac warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1740//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1740//console
This message is automatically generated.
send Cache-Control header on JSP pages
--
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Attachments: HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9027) Build fails on Windows without sh/sed/echo in the path
[ https://issues.apache.org/jira/browse/HADOOP-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496867#comment-13496867 ] Chris Nauroth commented on HADOOP-9027: --- +1 for the patch Build fails on Windows without sh/sed/echo in the path -- Key: HADOOP-9027 URL: https://issues.apache.org/jira/browse/HADOOP-9027 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9027.branch-1-win.cleanbuild.2.patch, HADOOP-9027.branch-1-win.cleanbuild.patch Branch-1-win still has a dependency on a few unix tools in compile time. Tracking Jira to remove this dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8998) send Cache-Control header on JSP pages
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-8998:
---
Attachment: HADOOP-8998.patch
taking care of the javac warning
send Cache-Control header on JSP pages
--
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Attachments: HADOOP-8998.patch, HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8998) send Cache-Control header on JSP pages
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496883#comment-13496883
]
Eli Collins commented on HADOOP-8998:
-
{quote}
IMO all HTTP responses by Hadoop (web UI, JSON, WebHDFS, HFTP, etc) should set
headers to disable caching because all these resources are dynamic by nature.
{quote}
Agree.+1 to the latest patch.
send Cache-Control header on JSP pages
--
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Attachments: HADOOP-8998.patch, HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8456) Support spaces in user names and group names in results returned via winutils
[ https://issues.apache.org/jira/browse/HADOOP-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496886#comment-13496886 ] Ivan Mitic commented on HADOOP-8456: Allen, Daryn, Vinod, please let me know if you have any additional feedback on the patch. Support spaces in user names and group names in results returned via winutils - Key: HADOOP-8456 URL: https://issues.apache.org/jira/browse/HADOOP-8456 Project: Hadoop Common Issue Type: Bug Components: native Affects Versions: 1-win Reporter: Chuan Liu Assignee: Ivan Mitic Priority: Minor Attachments: HADOOP-8456.branch-1-win.spaces.2.patch, HADOOP-8456.branch-1-win.spaces.patch When parsing results returned by ‘ls’, we made implicit assumption that user and group names cannot contain spaces. On Linux, spaces are not allowed in user names and group names. This is not the case for Windows. We need to find a way to fix the problem for Windows. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8998) send Cache-Control header on JSP pages
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496888#comment-13496888
]
Hadoop QA commented on HADOOP-8998:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553455/HADOOP-8998.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1741//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1741//console
This message is automatically generated.
send Cache-Control header on JSP pages
--
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Attachments: HADOOP-8998.patch, HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8998) set Cache-Control no-cache header on all dynamic content
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-8998:
---
Summary: set Cache-Control no-cache header on all dynamic content (was:
send Cache-Control header on JSP pages)
set Cache-Control no-cache header on all dynamic content
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Attachments: HADOOP-8998.patch, HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8998) set Cache-Control no-cache header on all dynamic content
[
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-8998:
---
Resolution: Fixed
Fix Version/s: 2.0.3-alpha
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
committed to trunk and branch-2
set Cache-Control no-cache header on all dynamic content
Key: HADOOP-8998
URL: https://issues.apache.org/jira/browse/HADOOP-8998
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Andy Isaacson
Assignee: Alejandro Abdelnur
Priority: Minor
Fix For: 2.0.3-alpha
Attachments: HADOOP-8998.patch, HADOOP-8998.patch
We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant
caches can properly manage cached data.
Currently our JSPs send:
{noformat}
% curl -v http://nn1:50070/dfshealth.jsp
...
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
Content-Length: 3651
Server: Jetty(6.1.26)
{noformat}
Based on a quick reading of RFC 2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to
send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty
docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate
this is fairly straightforward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
