[jira] [Updated] (HADOOP-8279) Auto-HA: Allow manual failover to be invoked from zkfc.
[ https://issues.apache.org/jira/browse/HADOOP-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-8279: Attachment: hadoop-8279.txt New rev fixes a number of issues: - when ZKFC makes RPCs to the NN, it has to switch to its own UGI, so it has the right krb credentials - add a service ACL for ZKProtocol - fix a potential deadlock with lock inversion in waitForActiveAttempt I did some testing by running a pseudo-distributed secure cluster, and doing a failover back and forth in a while loop from another shell. Ran a couple hundred of these successfully. Also tested behavior when one of the NNs was down, etc. I also ran one of the zkfcs under jcarder to look for potential deadlocks (only found the one mentioned above) Will continue testing this tomorrow, and also do some code cleanup. Mingjie, if you have a chance to test this, would love to hear how it works for you. Auto-HA: Allow manual failover to be invoked from zkfc. --- Key: HADOOP-8279 URL: https://issues.apache.org/jira/browse/HADOOP-8279 Project: Hadoop Common Issue Type: Improvement Components: ha Affects Versions: Auto Failover (HDFS-3042) Reporter: Mingjie Lai Assignee: Todd Lipcon Fix For: Auto Failover (HDFS-3042) Attachments: hadoop-8279.txt, hadoop-8279.txt HADOOP-8247 introduces a configure flag to prevent potential status inconsistency between zkfc and namenode, by making auto and manual failover mutually exclusive. However, as described in 2.7.2 section of design doc at HDFS-2185, we should allow manual and auto failover co-exist, by: - adding some rpc interfaces at zkfc - manual failover shall be triggered by haadmin, and handled by zkfc if auto failover is enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8296) yarn daemonlog usage wrong
[ https://issues.apache.org/jira/browse/HADOOP-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258051#comment-13258051 ] Devaraj K commented on HADOOP-8296: --- Moving it to common since it is issue in other components as well and changes involve in common. yarn daemonlog usage wrong --- Key: HADOOP-8296 URL: https://issues.apache.org/jira/browse/HADOOP-8296 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.2, 2.0.0, 3.0.0 Reporter: Thomas Graves Priority: Minor $ yarn daemonlog USAGES: java org.apache.hadoop.log.LogLevel -getlevel host:port name java org.apache.hadoop.log.LogLevel -setlevel host:port name level The usage shouldn't print java org.apache.hadoop.log.LogLevel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Moved] (HADOOP-8296) yarn daemonlog usage wrong
[ https://issues.apache.org/jira/browse/HADOOP-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K moved MAPREDUCE-3957 to HADOOP-8296: -- Component/s: (was: mrv2) Target Version/s: (was: trunk, 2.0.0) Affects Version/s: (was: 0.23.0) 3.0.0 2.0.0 0.23.2 Key: HADOOP-8296 (was: MAPREDUCE-3957) Project: Hadoop Common (was: Hadoop Map/Reduce) yarn daemonlog usage wrong --- Key: HADOOP-8296 URL: https://issues.apache.org/jira/browse/HADOOP-8296 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.2, 2.0.0, 3.0.0 Reporter: Thomas Graves Priority: Minor $ yarn daemonlog USAGES: java org.apache.hadoop.log.LogLevel -getlevel host:port name java org.apache.hadoop.log.LogLevel -setlevel host:port name level The usage shouldn't print java org.apache.hadoop.log.LogLevel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8296) hadoop/yarn daemonlog usage wrong
[ https://issues.apache.org/jira/browse/HADOOP-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated HADOOP-8296: -- Assignee: Devaraj K Summary: hadoop/yarn daemonlog usage wrong (was: yarn daemonlog usage wrong ) hadoop/yarn daemonlog usage wrong -- Key: HADOOP-8296 URL: https://issues.apache.org/jira/browse/HADOOP-8296 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.2, 2.0.0, 3.0.0 Reporter: Thomas Graves Assignee: Devaraj K Priority: Minor $ yarn daemonlog USAGES: java org.apache.hadoop.log.LogLevel -getlevel host:port name java org.apache.hadoop.log.LogLevel -setlevel host:port name level The usage shouldn't print java org.apache.hadoop.log.LogLevel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8296) hadoop/yarn daemonlog usage wrong
[ https://issues.apache.org/jira/browse/HADOOP-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated HADOOP-8296: -- Attachment: HADOOP-8296.patch hadoop/yarn daemonlog usage wrong -- Key: HADOOP-8296 URL: https://issues.apache.org/jira/browse/HADOOP-8296 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.2, 2.0.0, 3.0.0 Reporter: Thomas Graves Assignee: Devaraj K Priority: Minor Attachments: HADOOP-8296.patch $ yarn daemonlog USAGES: java org.apache.hadoop.log.LogLevel -getlevel host:port name java org.apache.hadoop.log.LogLevel -setlevel host:port name level The usage shouldn't print java org.apache.hadoop.log.LogLevel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8296) hadoop/yarn daemonlog usage wrong
[ https://issues.apache.org/jira/browse/HADOOP-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated HADOOP-8296: -- Status: Patch Available (was: Open) Attached patch to address this issue. hadoop/yarn daemonlog usage wrong -- Key: HADOOP-8296 URL: https://issues.apache.org/jira/browse/HADOOP-8296 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.2, 2.0.0, 3.0.0 Reporter: Thomas Graves Assignee: Devaraj K Priority: Minor Attachments: HADOOP-8296.patch $ yarn daemonlog USAGES: java org.apache.hadoop.log.LogLevel -getlevel host:port name java org.apache.hadoop.log.LogLevel -setlevel host:port name level The usage shouldn't print java org.apache.hadoop.log.LogLevel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8296) hadoop/yarn daemonlog usage wrong
[ https://issues.apache.org/jira/browse/HADOOP-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258061#comment-13258061 ] Hadoop QA commented on HADOOP-8296: --- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523460/HADOOP-8296.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.fs.viewfs.TestViewFsTrash +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/872//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/872//console This message is automatically generated. hadoop/yarn daemonlog usage wrong -- Key: HADOOP-8296 URL: https://issues.apache.org/jira/browse/HADOOP-8296 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.2, 2.0.0, 3.0.0 Reporter: Thomas Graves Assignee: Devaraj K Priority: Minor Attachments: HADOOP-8296.patch $ yarn daemonlog USAGES: java org.apache.hadoop.log.LogLevel -getlevel host:port name java org.apache.hadoop.log.LogLevel -setlevel host:port name level The usage shouldn't print java org.apache.hadoop.log.LogLevel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8148) Zero-copy ByteBuffer-based compressor / decompressor API
[ https://issues.apache.org/jira/browse/HADOOP-8148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258063#comment-13258063 ] Tim Broberg commented on HADOOP-8148: - bq. Sorry for my ignorance in this area, but: this implies that hardware codecs are pipelined? In the LineReader use case, you're saying you would provide a much larger block to the codec ahead of what is being read out of the decompression side? Yes, command/result handling, DMA transfer, and processing happen in parallel, which is crucial for small-packet performance. Given what I expect will be 32kB - 128kB blocks here, this isn't as huge an issue, but it's still non-trivial. The important pipelining, will be performing stream io in parallel with (de)compression. In addition to pipelining, there is parallelism. Non-low-end processors are multicore such that we will want to read several blocks ahead and process them in parallel. (One could also perform multithreaded software (de)compression in much the same fashion, but I have no plans to implement it.) So, yes, the HW version of the CompressionInputStream would have a separate thread which preemptively reads records in and drops them in an input queue, plugging when that queue is full. HW processes blocks from the input queue dumping results in an output queue which feeds the read() call. So, the HW is dumping stuff into buffers before the read() gets a chance to provide one. Zero-copy ByteBuffer-based compressor / decompressor API Key: HADOOP-8148 URL: https://issues.apache.org/jira/browse/HADOOP-8148 Project: Hadoop Common Issue Type: New Feature Components: io Reporter: Tim Broberg Assignee: Tim Broberg Attachments: hadoop8148.patch Per Todd Lipcon's comment in HDFS-2834, Whenever a native decompression codec is being used, ... we generally have the following copies: 1) Socket - DirectByteBuffer (in SocketChannel implementation) 2) DirectByteBuffer - byte[] (in SocketInputStream) 3) byte[] - Native buffer (set up for decompression) 4*) decompression to a different native buffer (not really a copy - decompression necessarily rewrites) 5) native buffer - byte[] with the proposed improvement we can hopefully eliminate #2,#3 for all applications, and #2,#3,and #5 for libhdfs. The interfaces in the attached patch attempt to address: A - Compression and decompression based on ByteBuffers (HDFS-2834) B - Zero-copy compression and decompression (HDFS-3051) C - Provide the caller a way to know how the max space required to hold compressed output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8297) Writable javadocs don't carry default constructor
[ https://issues.apache.org/jira/browse/HADOOP-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HADOOP-8297: Attachment: HADOOP-8297.patch Patch that adds this in, along with some extra whitespace removal from that chunk of the javadoc. Writable javadocs don't carry default constructor - Key: HADOOP-8297 URL: https://issues.apache.org/jira/browse/HADOOP-8297 Project: Hadoop Common Issue Type: Improvement Components: io Affects Versions: 2.0.0 Reporter: Harsh J Assignee: Harsh J Priority: Trivial Attachments: HADOOP-8297.patch The Writable API docs have a custom writable example but doesn't carry a default constructor in it. Apparently a default constructor is required and hence the example ought to carry it for benefit of the reader/paster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8297) Writable javadocs don't carry default constructor
[ https://issues.apache.org/jira/browse/HADOOP-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HADOOP-8297: Status: Patch Available (was: Open) Writable javadocs don't carry default constructor - Key: HADOOP-8297 URL: https://issues.apache.org/jira/browse/HADOOP-8297 Project: Hadoop Common Issue Type: Improvement Components: io Affects Versions: 2.0.0 Reporter: Harsh J Assignee: Harsh J Priority: Trivial Attachments: HADOOP-8297.patch The Writable API docs have a custom writable example but doesn't carry a default constructor in it. Apparently a default constructor is required and hence the example ought to carry it for benefit of the reader/paster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8297) Writable javadocs don't carry default constructor
[ https://issues.apache.org/jira/browse/HADOOP-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258147#comment-13258147 ] Hadoop QA commented on HADOOP-8297: --- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523479/HADOOP-8297.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/873//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/873//console This message is automatically generated. Writable javadocs don't carry default constructor - Key: HADOOP-8297 URL: https://issues.apache.org/jira/browse/HADOOP-8297 Project: Hadoop Common Issue Type: Improvement Components: io Affects Versions: 2.0.0 Reporter: Harsh J Assignee: Harsh J Priority: Trivial Attachments: HADOOP-8297.patch The Writable API docs have a custom writable example but doesn't carry a default constructor in it. Apparently a default constructor is required and hence the example ought to carry it for benefit of the reader/paster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8297) Writable javadocs don't carry default constructor
[ https://issues.apache.org/jira/browse/HADOOP-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HADOOP-8297: Component/s: (was: io) documentation Writable javadocs don't carry default constructor - Key: HADOOP-8297 URL: https://issues.apache.org/jira/browse/HADOOP-8297 Project: Hadoop Common Issue Type: Improvement Components: documentation Affects Versions: 2.0.0 Reporter: Harsh J Assignee: Harsh J Priority: Trivial Attachments: HADOOP-8297.patch The Writable API docs have a custom writable example but doesn't carry a default constructor in it. Apparently a default constructor is required and hence the example ought to carry it for benefit of the reader/paster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8288) Remove references of mapred.child.ulimit etc. since they are not being used any more
[ https://issues.apache.org/jira/browse/HADOOP-8288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258193#comment-13258193 ] Hudson commented on HADOOP-8288: Integrated in Hadoop-Hdfs-0.23-Build #233 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/233/]) svn merge -c 1328018 from trunk. FIXES: HADOOP-8288. Remove references of mapred.child.ulimit etc. since they are not being used any more (Ravi Prakash via bobby) (Revision 1328022) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1328022 Files : * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/packages/templates/conf/mapred-site.xml * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/site/apt/DeprecatedProperties.apt.vm * /hadoop/common/branches/branch-0.23/hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/streaming/TestUlimit.java * /hadoop/common/branches/branch-0.23/hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/streaming/UlimitApp.java Remove references of mapred.child.ulimit etc. since they are not being used any more Key: HADOOP-8288 URL: https://issues.apache.org/jira/browse/HADOOP-8288 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.2 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.3, 2.0.0, 3.0.0 Attachments: HADOOP-8288.branch-0.23.patch, HADOOP-8288.branch-0.23.patch Courtesy Philip Su, we found that (mapred.child.ulimit, mapreduce.map.ulimit, mapreduce.reduce.ulimit) were not being used at all. The configuration exists but is never used. Its also mentioned in mapred-default.xml and templates/../mapred-site.xml . Also the method getUlimitMemoryCommand in Shell.java is now useless and can be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7350) Use ServiceLoader to discover compression codec classes
[ https://issues.apache.org/jira/browse/HADOOP-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258206#comment-13258206 ] Hudson commented on HADOOP-7350: Integrated in Hadoop-Hdfs-trunk #1020 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1020/]) HADOOP-7350. Use ServiceLoader to discover compression codec classes. (Revision 1328083) Result = FAILURE tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1328083 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/io/compress/CompressionCodecFactory.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/resources/META-INF/services/org.apache.hadoop.io.compress.CompressionCodec * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/compress/TestCodecFactory.java Use ServiceLoader to discover compression codec classes --- Key: HADOOP-7350 URL: https://issues.apache.org/jira/browse/HADOOP-7350 Project: Hadoop Common Issue Type: Improvement Components: conf, io Reporter: Tom White Assignee: Tom White Fix For: 2.0.0 Attachments: HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch By using a ServiceLoader users wouldn't have to add codec classes to io.compression.codecs for codecs that aren't shipped with Hadoop (e.g. LZO), since they would be automatically picked up from the classpath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8288) Remove references of mapred.child.ulimit etc. since they are not being used any more
[ https://issues.apache.org/jira/browse/HADOOP-8288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258211#comment-13258211 ] Hudson commented on HADOOP-8288: Integrated in Hadoop-Hdfs-trunk #1020 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1020/]) HADOOP-8288. Remove references of mapred.child.ulimit etc. since they are not being used any more (Ravi Prakash via bobby) (Revision 1328018) Result = FAILURE bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1328018 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/util/Shell.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/packages/templates/conf/mapred-site.xml * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/apt/DeprecatedProperties.apt.vm * /hadoop/common/trunk/hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/streaming/TestUlimit.java * /hadoop/common/trunk/hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/streaming/UlimitApp.java Remove references of mapred.child.ulimit etc. since they are not being used any more Key: HADOOP-8288 URL: https://issues.apache.org/jira/browse/HADOOP-8288 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.2 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.3, 2.0.0, 3.0.0 Attachments: HADOOP-8288.branch-0.23.patch, HADOOP-8288.branch-0.23.patch Courtesy Philip Su, we found that (mapred.child.ulimit, mapreduce.map.ulimit, mapreduce.reduce.ulimit) were not being used at all. The configuration exists but is never used. Its also mentioned in mapred-default.xml and templates/../mapred-site.xml . Also the method getUlimitMemoryCommand in Shell.java is now useless and can be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7350) Use ServiceLoader to discover compression codec classes
[ https://issues.apache.org/jira/browse/HADOOP-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258227#comment-13258227 ] Hudson commented on HADOOP-7350: Integrated in Hadoop-Mapreduce-trunk #1055 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1055/]) HADOOP-7350. Use ServiceLoader to discover compression codec classes. (Revision 1328083) Result = FAILURE tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1328083 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/io/compress/CompressionCodecFactory.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/resources/META-INF/services/org.apache.hadoop.io.compress.CompressionCodec * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/compress/TestCodecFactory.java Use ServiceLoader to discover compression codec classes --- Key: HADOOP-7350 URL: https://issues.apache.org/jira/browse/HADOOP-7350 Project: Hadoop Common Issue Type: Improvement Components: conf, io Reporter: Tom White Assignee: Tom White Fix For: 2.0.0 Attachments: HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch By using a ServiceLoader users wouldn't have to add codec classes to io.compression.codecs for codecs that aren't shipped with Hadoop (e.g. LZO), since they would be automatically picked up from the classpath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8288) Remove references of mapred.child.ulimit etc. since they are not being used any more
[ https://issues.apache.org/jira/browse/HADOOP-8288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258232#comment-13258232 ] Hudson commented on HADOOP-8288: Integrated in Hadoop-Mapreduce-trunk #1055 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1055/]) HADOOP-8288. Remove references of mapred.child.ulimit etc. since they are not being used any more (Ravi Prakash via bobby) (Revision 1328018) Result = FAILURE bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1328018 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/util/Shell.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/packages/templates/conf/mapred-site.xml * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/apt/DeprecatedProperties.apt.vm * /hadoop/common/trunk/hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/streaming/TestUlimit.java * /hadoop/common/trunk/hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/streaming/UlimitApp.java Remove references of mapred.child.ulimit etc. since they are not being used any more Key: HADOOP-8288 URL: https://issues.apache.org/jira/browse/HADOOP-8288 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.2 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.3, 2.0.0, 3.0.0 Attachments: HADOOP-8288.branch-0.23.patch, HADOOP-8288.branch-0.23.patch Courtesy Philip Su, we found that (mapred.child.ulimit, mapreduce.map.ulimit, mapreduce.reduce.ulimit) were not being used at all. The configuration exists but is never used. Its also mentioned in mapred-default.xml and templates/../mapred-site.xml . Also the method getUlimitMemoryCommand in Shell.java is now useless and can be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8294) IPC Connection becomes unusable even if server address was temporarilly unresolvable
[ https://issues.apache.org/jira/browse/HADOOP-8294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258279#comment-13258279 ] Kihwal Lee commented on HADOOP-8294: Manually ran test patch [exec] -1 overall. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] -1 findbugs. The patch appears to introduce 8 new Findbugs (version 1.3.9) warnings. The number of findbugs warnings actually didn't increase. IPC Connection becomes unusable even if server address was temporarilly unresolvable Key: HADOOP-8294 URL: https://issues.apache.org/jira/browse/HADOOP-8294 Project: Hadoop Common Issue Type: Bug Components: ipc Affects Versions: 1.0.2 Reporter: Kihwal Lee Assignee: Kihwal Lee Priority: Critical Fix For: 1.0.3, 1.1.0 Attachments: hadoop-8294.patch This is same as HADOOP-7428, but was observed on 1.x data nodes. This can happen more frequently after HADOOP-7472, which allows IPC Connection to re-resolve the name. HADOOP-7428 needs to be back-ported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8293) The native library's Makefile.am doesn't include JNI path
[ https://issues.apache.org/jira/browse/HADOOP-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258347#comment-13258347 ] Matt Foley commented on HADOOP-8293: +1. Looks right. Thanks. The native library's Makefile.am doesn't include JNI path - Key: HADOOP-8293 URL: https://issues.apache.org/jira/browse/HADOOP-8293 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Owen O'Malley Assignee: Owen O'Malley Fix For: 1.0.3, 3.0.0 Attachments: h-8293.patch When compiling on centos 6, I get the following error when compiling the native library: {code} [exec] /usr/bin/ld: cannot find -ljvm {code} The problem is simply that the Makefile.am libhadoop_la_LDFLAGS doesn't include AM_LDFLAGS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Attachment: hadoop-8285-3-common.patch Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Target Version/s: 2.0.0, 3.0.0 (was: 3.0.0, 2.0.0) Status: Open (was: Patch Available) Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Attachment: hadoop-8285-3.patch Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258398#comment-13258398 ] Hadoop QA commented on HADOOP-8285: --- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523523/hadoop-8285-3-common.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 5 new or modified test files. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. -1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/874//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HADOOP-Build/874//artifact/trunk/hadoop-common-project/patchprocess/newPatchFindbugsWarningshadoop-common.html Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/874//console This message is automatically generated. Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7426) User Guide for how to use viewfs with federation
[ https://issues.apache.org/jira/browse/HADOOP-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HADOOP-7426: Component/s: documentation Target Version/s: 2.0.0 Affects Version/s: 2.0.0 Would be great to get this in before 2.0 User Guide for how to use viewfs with federation Key: HADOOP-7426 URL: https://issues.apache.org/jira/browse/HADOOP-7426 Project: Hadoop Common Issue Type: Improvement Components: documentation Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Minor Attachments: Viewfs Guide.pdf, c7426_20111214.patch, c7426_20111215.patch, c7426_20111215b.patch, c7426_20111218.patch, c7426_20111220.patch, c7426_20111220_site.tar.gz, viewfs_TypicalMountTable.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8298) ViewFs merge mounts
Eli Collins created HADOOP-8298: --- Summary: ViewFs merge mounts Key: HADOOP-8298 URL: https://issues.apache.org/jira/browse/HADOOP-8298 Project: Hadoop Common Issue Type: New Feature Components: fs Affects Versions: 2.0.0 Reporter: Eli Collins A merge mount is a single mount represented by the union of two namespaces. See the viewfs docs (HADOOP-7426) and [ViewFs javadoc|http://hadoop.apache.org/common/docs/r0.23.0/api/org/apache/hadoop/fs/viewfs/ViewFs.html] for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8299) ViewFs doesn't work with a slash mount point
Eli Collins created HADOOP-8299: --- Summary: ViewFs doesn't work with a slash mount point Key: HADOOP-8299 URL: https://issues.apache.org/jira/browse/HADOOP-8299 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 2.0.0 Reporter: Eli Collins We currently assume [a typical viewfs client configuration|https://issues.apache.org/jira/secure/attachment/12507504/viewfs_TypicalMountTable.png] is a set of non-overlapping mounts. This means every time you want to add a new top-level directory you need to update the client-side mountable config. If users could specify a slash mount, and then add additional mounts as necessary they could add a new top-level directory without updating all client configs (as long as the new top-level directory was being created on the NN the slash mount points to). This could be achieved by HADOOP-8298 (merge mounts, since we're effectively merging all new mount points with slash) or having the notion of a default NN for a mount table. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8299) ViewFs doesn't work with a slash mount point
[ https://issues.apache.org/jira/browse/HADOOP-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258597#comment-13258597 ] Eli Collins commented on HADOOP-8299: - Here's the exception you get btw if you try to create a slash mount entry. We should make this a more friendly error message in the mean time. {noformat} java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.hadoop.fs.viewfs.InodeTree.createLink(InodeTree.java:237) at org.apache.hadoop.fs.viewfs.InodeTree.init(InodeTree.java:334) at org.apache.hadoop.fs.viewfs.ViewFileSystem$1.init(ViewFileSystem.java:165) at org.apache.hadoop.fs.viewfs.ViewFileSystem.initialize(ViewFileSystem.java:165) at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2041) at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:78) at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2075) at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2057) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:284) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:151) {noformat} ViewFs doesn't work with a slash mount point Key: HADOOP-8299 URL: https://issues.apache.org/jira/browse/HADOOP-8299 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 2.0.0 Reporter: Eli Collins We currently assume [a typical viewfs client configuration|https://issues.apache.org/jira/secure/attachment/12507504/viewfs_TypicalMountTable.png] is a set of non-overlapping mounts. This means every time you want to add a new top-level directory you need to update the client-side mountable config. If users could specify a slash mount, and then add additional mounts as necessary they could add a new top-level directory without updating all client configs (as long as the new top-level directory was being created on the NN the slash mount points to). This could be achieved by HADOOP-8298 (merge mounts, since we're effectively merging all new mount points with slash) or having the notion of a default NN for a mount table. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HADOOP-8285: --- Component/s: ipc Target Version/s: 2.0.0, 3.0.0 (was: 3.0.0, 2.0.0) Hadoop Flags: Reviewed {code} + Class name=~org\.apache\.hadoop\.ha\.proto\.RpcPayloadHeaderProtos.*/ {code} The package should be hadoop.ipc.protobuf. +1 once the above has been fixed. Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Attachment: hadoop-8285-4.patch Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Target Version/s: 2.0.0, 3.0.0 (was: 3.0.0, 2.0.0) Status: Patch Available (was: Open) Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Target Version/s: 2.0.0, 3.0.0 (was: 3.0.0, 2.0.0) Status: Open (was: Patch Available) Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Attachment: hadoop-8285-4-common.patch Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258699#comment-13258699 ] Hadoop QA commented on HADOOP-8285: --- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523597/hadoop-8285-4-common.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 5 new or modified test files. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/875//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/875//console This message is automatically generated. Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8279) Auto-HA: Allow manual failover to be invoked from zkfc.
[ https://issues.apache.org/jira/browse/HADOOP-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-8279: Attachment: hadoop-8279.txt This rev should be ready for review. I did a bunch more testing, cleaned up the code with javadocs, comments, etc. I also manually tested with security, ACLs, etc, verified everything worked as expected. I also ran the zkfc manually through jcarder while doing these tests and verified no lock cycles. Auto-HA: Allow manual failover to be invoked from zkfc. --- Key: HADOOP-8279 URL: https://issues.apache.org/jira/browse/HADOOP-8279 Project: Hadoop Common Issue Type: Improvement Components: ha Affects Versions: Auto Failover (HDFS-3042) Reporter: Mingjie Lai Assignee: Todd Lipcon Fix For: Auto Failover (HDFS-3042) Attachments: hadoop-8279.txt, hadoop-8279.txt, hadoop-8279.txt HADOOP-8247 introduces a configure flag to prevent potential status inconsistency between zkfc and namenode, by making auto and manual failover mutually exclusive. However, as described in 2.7.2 section of design doc at HDFS-2185, we should allow manual and auto failover co-exist, by: - adding some rpc interfaces at zkfc - manual failover shall be triggered by haadmin, and handled by zkfc if auto failover is enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira