[jira] [Updated] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9752: -- Attachment: HADOOP-9752v4.patch Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9752v1.patch, HADOOP-9752v2.patch, HADOOP-9752v3.patch, HADOOP-9752v4.patch, HADOOP-9752v4.patch This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13801989#comment-13801989 ] Robert Parker commented on HADOOP-9752: --- I have run the 5 tests that failed on a Fedora VM and the tests all pass, but it does bother me that TestNodeManagerShutdown failed on the patch build. Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9752v1.patch, HADOOP-9752v2.patch, HADOOP-9752v3.patch, HADOOP-9752v4.patch This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9752: -- Status: Open (was: Patch Available) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 2.0.4-alpha, 3.0.0 Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9752v1.patch, HADOOP-9752v2.patch, HADOOP-9752v3.patch, HADOOP-9752v4.patch This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9752: -- Status: Patch Available (was: Open) firing the jenkins build again Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 2.0.4-alpha, 3.0.0 Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9752v1.patch, HADOOP-9752v2.patch, HADOOP-9752v3.patch, HADOOP-9752v4.patch This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9016) Provide unit tests for class org.apache.hadoop.fs.HarFileSystem.HarFSDataInputStream
[ https://issues.apache.org/jira/browse/HADOOP-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796849#comment-13796849 ] Robert Parker commented on HADOOP-9016: --- Thanks for the patch [~iveselovsky] +1 (non-binding) lgtm Provide unit tests for class org.apache.hadoop.fs.HarFileSystem.HarFSDataInputStream - Key: HADOOP-9016 URL: https://issues.apache.org/jira/browse/HADOOP-9016 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.3.0 Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Priority: Minor Attachments: HADOOP-9016--b.patch, HADOOP-9016-branch-0.23--d.patch, HADOOP-9016-branch-0.23--e.patch, HADOOP-9016--c.patch, HADOOP-9016--d.patch, HADOOP-9016--e.patch, HADOOP-9016--f.patch, HADOOP-9016.patch unit-test coverage of classes org.apache.hadoop.fs.HarFileSystem.HarFSDataInputStream, org.apache.hadoop.fs.HarFileSystem.HarFSDataInputStream.HarFsInputStream is zero. Suggested to provide unit-tests covering these classes. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-9078) enhance unit-test coverage of class org.apache.hadoop.fs.FileContext
[ https://issues.apache.org/jira/browse/HADOOP-9078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9078: -- Attachment: HADOOP-9078-trunk--N9.patch enhance unit-test coverage of class org.apache.hadoop.fs.FileContext Key: HADOOP-9078 URL: https://issues.apache.org/jira/browse/HADOOP-9078 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Attachments: HADOOP-9078--b.patch, HADOOP-9078-branch-0.23.patch, HADOOP-9078-branch-2--b.patch, HADOOP-9078-branch-2--c.patch, HADOOP-9078-branch-2--N1.patch, HADOOP-9078-branch-2--N2.patch, HADOOP-9078-branch-2--N3.patch, HADOOP-9078-branch-2--N4.patch, HADOOP-9078-branch-2.patch, HADOOP-9078.patch, HADOOP-9078-patch-from-[trunk-gd]-to-[fb-HADOOP-9078-trunk-gd]-N1.patch, HADOOP-9078-trunk--N1.patch, HADOOP-9078-trunk--N2.patch, HADOOP-9078-trunk--N6.patch, HADOOP-9078-trunk--N8.patch, HADOOP-9078-trunk--N9.patch -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9078) enhance unit-test coverage of class org.apache.hadoop.fs.FileContext
[ https://issues.apache.org/jira/browse/HADOOP-9078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796906#comment-13796906 ] Robert Parker commented on HADOOP-9078: --- [~iveselovsky], thanks for the patch. I corrected a spelling error and an unused import to create N9. lgtm +1 (non-binding) enhance unit-test coverage of class org.apache.hadoop.fs.FileContext Key: HADOOP-9078 URL: https://issues.apache.org/jira/browse/HADOOP-9078 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Attachments: HADOOP-9078--b.patch, HADOOP-9078-branch-0.23.patch, HADOOP-9078-branch-2--b.patch, HADOOP-9078-branch-2--c.patch, HADOOP-9078-branch-2--N1.patch, HADOOP-9078-branch-2--N2.patch, HADOOP-9078-branch-2--N3.patch, HADOOP-9078-branch-2--N4.patch, HADOOP-9078-branch-2.patch, HADOOP-9078.patch, HADOOP-9078-patch-from-[trunk-gd]-to-[fb-HADOOP-9078-trunk-gd]-N1.patch, HADOOP-9078-trunk--N1.patch, HADOOP-9078-trunk--N2.patch, HADOOP-9078-trunk--N6.patch, HADOOP-9078-trunk--N8.patch, HADOOP-9078-trunk--N9.patch -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9199) Cover package org.apache.hadoop.io with unit tests
[ https://issues.apache.org/jira/browse/HADOOP-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788323#comment-13788323 ] Robert Parker commented on HADOOP-9199: --- Thanks [~andrey]. +1 (non-binding) lgtm Cover package org.apache.hadoop.io with unit tests -- Key: HADOOP-9199 URL: https://issues.apache.org/jira/browse/HADOOP-9199 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Vadim Bondarev Assignee: Andrey Klochkov Attachments: HADOOP-9199-branch-0.23-a.patch, HADOOP-9199-branch-0.23-b.patch, HADOOP-9199-branch-0.23-c.patch, HADOOP-9199-branch-0.23-e.patch, HADOOP-9199-branch-2-a.patch, HADOOP-9199-branch-2-b.patch, HADOOP-9199-branch-2-c.patch, HADOOP-9199-branch-2-e.patch, HADOOP-9199-trunk-a.patch, HADOOP-9199-trunk-b.patch, HADOOP-9199-trunk-c.patch, HADOOP-9199-trunk-e.patch, HADOOP-9199-trunk--n6.patch, HADOOP-9199-trunk--n7.patch -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9752: -- Attachment: HADOOP-9752v3.patch Added comment to a java file in YARN to trigger the yarn unit tests. Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9752v1.patch, HADOOP-9752v2.patch, HADOOP-9752v3.patch This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9199) Cover package org.apache.hadoop.io with unit tests
[
https://issues.apache.org/jira/browse/HADOOP-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786325#comment-13786325
]
Robert Parker commented on HADOOP-9199:
---
[~aklochkov] mvn test -Dtest=TestMapFile; mvn test -Dtest=TestMapFile shows the
that TestMapFile is not quite cleaning up. Additionally the '/' is missing
between the test.build.data dir and the test file name.
{code}
Running org.apache.hadoop.io.TestMapFile
Tests run: 20, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 4.362 sec
FAILURE! - in org.apache.hadoop.io.TestMapFile
testRenameWithFalse(org.apache.hadoop.io.TestMapFile) Time elapsed: 2.37 sec
FAILURE!
junit.framework.AssertionFailedError: testRenameWithFalse invalid
IOExceptionMessage error !!!
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
org.apache.hadoop.io.TestMapFile.testRenameWithFalse(TestMapFile.java:255)
testRename(org.apache.hadoop.io.TestMapFile) Time elapsed: 0.04 sec
FAILURE!
junit.framework.AssertionFailedError: testRename error java.io.IOException:
Target
/home/rparker/Y/hadoop-gitdev/hadoop-common-project/hadoop-common/target/test/datatest-new.mapfile/datatest-old.mapfile
is a directory
at junit.framework.Assert.fail(Assert.java:50)
at org.apache.hadoop.io.TestMapFile.testRename(TestMapFile.java:199)
testRenameWithException(org.apache.hadoop.io.TestMapFile) Time elapsed: 0.037
sec FAILURE!
junit.framework.ComparisonFailure: testRenameWithException invalid
IOExceptionMessage !!! expected:[Target
/home/rparker/Y/hadoop-gitdev/hadoop-common-project/hadoop-common/target/test/datatest-new.mapfile/datatest-old.mapfile
is a directory] but was:[Can't rename file]
at junit.framework.Assert.assertEquals(Assert.java:85)
at
org.apache.hadoop.io.TestMapFile.testRenameWithException(TestMapFile.java:229)
Results :
Failed tests:
TestMapFile.testRenameWithFalse:255 testRenameWithFalse invalid
IOExceptionMessage error !!!
TestMapFile.testRename:199 testRename error java.io.IOException: Target
/home/rparker/Y/hadoop-gitdev/hadoop-common-project/hadoop-common/target/test/datatest-new.mapfile/datatest-old.mapfile
is a directory
TestMapFile.testRenameWithException:229 testRenameWithException invalid
IOExceptionMessage !!! expected:[Target
/home/rparker/Y/hadoop-gitdev/hadoop-common-project/hadoop-common/target/test/datatest-new.mapfile/datatest-old.mapfile
is a directory] but was:[Can't rename file]
Tests run: 20, Failures: 3, Errors: 0, Skipped: 0
{code}
The '/' is missing in several other tests (TestArrayFile,TestBloomMapFile),. I
used to notice the difference between TestSetFile (which is correct) and
TestMapFile
{code}
grep test.build.data
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestArrayFile.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestArrayWritable.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestBloomMapFile.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestBooleanWritable.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestBytesWritable.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestEnumSetWritable.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestMapFile.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestSetFile.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestText.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestCompressedWritable.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestMultipleIOException.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestNullWritable.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestOutputBuffer.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestTwoDArrayWritable.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestVLongWritable.java
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestWritableComparator.java
{code}
Thanks for correcting the 80 lines and please remove the tabs. Sorry I missed
these items on the first review.
Cover package org.apache.hadoop.io with unit tests
--
Key: HADOOP-9199
URL: https://issues.apache.org/jira/browse/HADOOP-9199
Project: Hadoop Common
Issue Type: Test
Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6
Reporter: Vadim Bondarev
Assignee: Andrey Klochkov
Attachments: HADOOP-9199-branch-0.23-a.patch,
[jira] [Updated] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9752: -- Attachment: HADOOP-9752v4.patch Fixed the typo. Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9752v1.patch, HADOOP-9752v2.patch, HADOOP-9752v3.patch, HADOOP-9752v4.patch This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker reassigned HADOOP-9752: - Assignee: Robert Parker Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker Assignee: Robert Parker This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9752: -- Status: Patch Available (was: Open) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 2.0.4-alpha, 3.0.0 Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9752v1.patch This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9752: -- Attachment: HADOOP-9752v1.patch Touched the CHANGES.txt file in YARN to make those tests run on the pre-commit check. Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9752v1.patch This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9752: -- Attachment: HADOOP-9752v2.patch Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9752v1.patch, HADOOP-9752v2.patch This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9199) Cover package org.apache.hadoop.io with unit tests
[
https://issues.apache.org/jira/browse/HADOOP-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784054#comment-13784054
]
Robert Parker commented on HADOOP-9199:
---
[~vbondarev] thanks for the patch, one small change:
for the TestEnumWritable#testEnumSetWritableWriteRead:
The readFields operation should go to a new EnumWritableSet so the source
in not contaminated by the read. For example:
{code}
EnumSetWritableTestEnumSet eset =
new EnumSetWritableTestEnumSet(EnumSet.of(TestEnumSet.APPEND,
TestEnumSet.CREATE), TestEnumSet.class);
EnumSetWritableTestEnumSet oset = new EnumSetWritableTestEnumSet();
eset.write(out);
in.reset(out.getData(), out.getLength());
oset.readFields(in);
EnumSetTestEnumSet result = oset.get();
{code}
Cover package org.apache.hadoop.io with unit tests
--
Key: HADOOP-9199
URL: https://issues.apache.org/jira/browse/HADOOP-9199
Project: Hadoop Common
Issue Type: Test
Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6
Reporter: Vadim Bondarev
Assignee: Vadim Bondarev
Attachments: HADOOP-9199-branch-0.23-a.patch,
HADOOP-9199-branch-0.23-b.patch, HADOOP-9199-branch-0.23-c.patch,
HADOOP-9199-branch-0.23-e.patch, HADOOP-9199-branch-2-a.patch,
HADOOP-9199-branch-2-b.patch, HADOOP-9199-branch-2-c.patch,
HADOOP-9199-branch-2-e.patch, HADOOP-9199-trunk-a.patch,
HADOOP-9199-trunk-b.patch, HADOOP-9199-trunk-c.patch,
HADOOP-9199-trunk-e.patch
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HADOOP-9291) enhance unit-test coverage of package o.a.h.metrics2
[ https://issues.apache.org/jira/browse/HADOOP-9291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784106#comment-13784106 ] Robert Parker commented on HADOOP-9291: --- [~iveselovsky], unfortunately the patch is stale, sorry for the delay in reviewing. enhance unit-test coverage of package o.a.h.metrics2 Key: HADOOP-9291 URL: https://issues.apache.org/jira/browse/HADOOP-9291 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.7 Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Attachments: HADOOP-9291-branch-0.23--N4.patch, HADOOP-9291-trunk--N4.patch, HADOOP-9291-trunk--N5.patch, HADOOP-9291-trunk--N6.patch, HADOOP-9291-trunk--N6.patch -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9254) Cover packages org.apache.hadoop.util.bloom, org.apache.hadoop.util.hash
[ https://issues.apache.org/jira/browse/HADOOP-9254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784227#comment-13784227 ] Robert Parker commented on HADOOP-9254: --- Thanks [~vbondarev] for the patch. +1 (non-binding) lgtm Cover packages org.apache.hadoop.util.bloom, org.apache.hadoop.util.hash Key: HADOOP-9254 URL: https://issues.apache.org/jira/browse/HADOOP-9254 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Vadim Bondarev Assignee: Vadim Bondarev Attachments: HADOOP-9254-branch-0.23-a.patch, HADOOP-9254-branch-0.23-c.patch, HADOOP-9254-branch-2-a.patch, HADOOP-9254-branch-2-b.patch, HADOOP-9254-trunk-a.patch, HADOOP-9254-trunk-b.patch -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9016) Provide unit tests for class org.apache.hadoop.fs.HarFileSystem.HarFSDataInputStream
[ https://issues.apache.org/jira/browse/HADOOP-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784231#comment-13784231 ] Robert Parker commented on HADOOP-9016: --- Unfortunately the patch is stale, can you please update. Provide unit tests for class org.apache.hadoop.fs.HarFileSystem.HarFSDataInputStream - Key: HADOOP-9016 URL: https://issues.apache.org/jira/browse/HADOOP-9016 Project: Hadoop Common Issue Type: Improvement Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Priority: Minor Attachments: HADOOP-9016--b.patch, HADOOP-9016-branch-0.23--d.patch, HADOOP-9016-branch-0.23--e.patch, HADOOP-9016--c.patch, HADOOP-9016--d.patch, HADOOP-9016--e.patch, HADOOP-9016.patch unit-test coverage of classes org.apache.hadoop.fs.HarFileSystem.HarFSDataInputStream, org.apache.hadoop.fs.HarFileSystem.HarFSDataInputStream.HarFsInputStream is zero. Suggested to provide unit-tests covering these classes. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9063) enhance unit-test coverage of class org.apache.hadoop.fs.FileUtil
[ https://issues.apache.org/jira/browse/HADOOP-9063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783008#comment-13783008 ] Robert Parker commented on HADOOP-9063: --- +1 (non-binding) lgtm. I was able to apply the trunk patch to branch-2 and successfully test it(now). Recommend applying the trunk patch to branch-2 to avoid unnecessary divergence. enhance unit-test coverage of class org.apache.hadoop.fs.FileUtil - Key: HADOOP-9063 URL: https://issues.apache.org/jira/browse/HADOOP-9063 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Priority: Minor Attachments: HADOOP-9063--b.patch, HADOOP-9063-branch-0.23--b.patch, HADOOP-9063-branch-0.23--c.patch, HADOOP-9063-branch-2--N1.patch, HADOOP-9063-branch-2--N2.patch, HADOOP-9063.patch, HADOOP-9063-trunk--c.patch, HADOOP-9063-trunk--c.patch, HADOOP-9063-trunk--N2.patch, HADOOP-9063-trunk--N3.patch, HADOOP-9063-trunk--N6.patch Some methods of class org.apache.hadoop.fs.FileUtil are covered by unit-tests poorly or not covered at all. Enhance the coverage. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9078) enhance unit-test coverage of class org.apache.hadoop.fs.FileContext
[ https://issues.apache.org/jira/browse/HADOOP-9078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783392#comment-13783392 ] Robert Parker commented on HADOOP-9078: --- Thanks [~dennisyv] and [~iveselovsky] for the patches. Both the branch-2 and trunk patches apply to trunk fine (as all the affected files are identical in both branch-2 and trunk). But patches are different, for example FileContextMainOperationsBaseTest.java is different for testWorkingDirectory. Please reconcile these patches so they are making the same change. enhance unit-test coverage of class org.apache.hadoop.fs.FileContext Key: HADOOP-9078 URL: https://issues.apache.org/jira/browse/HADOOP-9078 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Attachments: HADOOP-9078--b.patch, HADOOP-9078-branch-0.23.patch, HADOOP-9078-branch-2--b.patch, HADOOP-9078-branch-2--c.patch, HADOOP-9078-branch-2--N1.patch, HADOOP-9078-branch-2--N2.patch, HADOOP-9078-branch-2--N3.patch, HADOOP-9078-branch-2--N4.patch, HADOOP-9078-branch-2.patch, HADOOP-9078.patch, HADOOP-9078-patch-from-[trunk-gd]-to-[fb-HADOOP-9078-trunk-gd]-N1.patch, HADOOP-9078-trunk--N1.patch, HADOOP-9078-trunk--N2.patch, HADOOP-9078-trunk--N6.patch, HADOOP-9078-trunk--N8.patch -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[
https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774818#comment-13774818
]
Robert Parker commented on HADOOP-9752:
---
Downloaded 3.3.8 and tested the kill, seems to work
{noformat}
~/Downloads/procps-ng-3.3.8
⍉
▶ ps -ef | grep rparker | grep sublime
rparker 10557 8903 0 18:05 pts/600:00:00 grep sublime
rparker 13541 1 0 Sep20 ?00:00:09 /opt/sublime_text/sublime_text
rparker 13555 13541 0 Sep20 ?00:00:00 /opt/sublime_text/plugin_host
13541
~/Downloads/procps-ng-3.3.8
▶ ./kill --version
lt-kill from procps-ng 3.3.8
~/Downloads/procps-ng-3.3.8
▶ ./kill -13541
{noformat}
Latest Ubuntu (13.04) /bin/kill parameter for process group requires a
'double dash kill -0 -- -pid
--
Key: HADOOP-9752
URL: https://issues.apache.org/jira/browse/HADOOP-9752
Project: Hadoop Common
Issue Type: Bug
Components: util
Affects Versions: 3.0.0, 2.0.4-alpha
Reporter: Robert Parker
This changed on Ubuntu 12.10 and later. This prevents the kill command from
executing correctly in Shell.java.
There is a bug filed in Ubuntu but there is not much activity.
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796
--
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-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766423#comment-13766423 ] Robert Parker commented on HADOOP-9752: --- This appears to be a bug in procps-ng based on http://www.freelists.org/post/procps/PATCH-33-kill-fix-PID-handling, and has been fixed in procps-ng-3.3.4 according to https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796. I will download that version and test. Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- 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-8315) Support SASL-authenticated ZooKeeper in ActiveStandbyElector
[ https://issues.apache.org/jira/browse/HADOOP-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8315: -- Attachment: hadoop-8315_v2.txt Refreshed the patch. Support SASL-authenticated ZooKeeper in ActiveStandbyElector Key: HADOOP-8315 URL: https://issues.apache.org/jira/browse/HADOOP-8315 Project: Hadoop Common Issue Type: Improvement Components: auto-failover, ha Affects Versions: Auto Failover (HDFS-3042) Reporter: Todd Lipcon Assignee: Todd Lipcon Attachments: hadoop-8315.txt, hadoop-8315_v2.txt Currently, if you try to use SASL-authenticated ZK with the ActiveStandbyElector, you run into a couple issues: 1) We hit ZOOKEEPER-1437 - we need to wait until we see SaslAuthenticated before we can make any requests 2) We currently throw a fatalError when we see the SaslAuthenticated callback on the connection watcher We need to wait for ZK-1437 upstream, and then upgrade to the fixed version for #1. For #2 we just need to add a case there and ignore it. -- 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-9476) Some test cases in TestUserGroupInformation fail if ran after testSetLoginUser.
[ https://issues.apache.org/jira/browse/HADOOP-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9476: -- Assignee: Robert Parker Some test cases in TestUserGroupInformation fail if ran after testSetLoginUser. --- Key: HADOOP-9476 URL: https://issues.apache.org/jira/browse/HADOOP-9476 Project: Hadoop Common Issue Type: Bug Components: security, test Affects Versions: 3.0.0, 0.23.7, 2.0.4-alpha Reporter: Kihwal Lee Assignee: Robert Parker HADOOP-9352 added a new test case testSetLoginUser. If it runs prior to other test cases, some of them fail. -- 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-9476) Some test cases in TestUserGroupInformation fail if ran after testSetLoginUser.
[ https://issues.apache.org/jira/browse/HADOOP-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9476: -- Target Version/s: 0.23.10 In JDK7 the last test tends to run first (order appears not to be guaranteed) and the setLoginUser then affects the remaining tests. Added a after method to set the user to null which I copied from trunk. Some test cases in TestUserGroupInformation fail if ran after testSetLoginUser. --- Key: HADOOP-9476 URL: https://issues.apache.org/jira/browse/HADOOP-9476 Project: Hadoop Common Issue Type: Bug Components: security, test Affects Versions: 3.0.0, 0.23.7, 2.0.4-alpha Reporter: Kihwal Lee Assignee: Robert Parker Attachments: HADOOP-9476-br0.23.patch HADOOP-9352 added a new test case testSetLoginUser. If it runs prior to other test cases, some of them fail. -- 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-9476) Some test cases in TestUserGroupInformation fail if ran after testSetLoginUser.
[ https://issues.apache.org/jira/browse/HADOOP-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9476: -- Attachment: HADOOP-9476-br0.23.patch Some test cases in TestUserGroupInformation fail if ran after testSetLoginUser. --- Key: HADOOP-9476 URL: https://issues.apache.org/jira/browse/HADOOP-9476 Project: Hadoop Common Issue Type: Bug Components: security, test Affects Versions: 3.0.0, 0.23.7, 2.0.4-alpha Reporter: Kihwal Lee Assignee: Robert Parker Attachments: HADOOP-9476-br0.23.patch HADOOP-9352 added a new test case testSetLoginUser. If it runs prior to other test cases, some of them fail. -- 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-9476) Some test cases in TestUserGroupInformation fail if ran after testSetLoginUser.
[ https://issues.apache.org/jira/browse/HADOOP-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9476: -- Affects Version/s: (was: 2.0.4-alpha) (was: 3.0.0) Status: Patch Available (was: Open) Branch-2 and trunk have added the before and after methods to clean up the UGI. This patch is only for branch-0.23 Some test cases in TestUserGroupInformation fail if ran after testSetLoginUser. --- Key: HADOOP-9476 URL: https://issues.apache.org/jira/browse/HADOOP-9476 Project: Hadoop Common Issue Type: Bug Components: security, test Affects Versions: 0.23.7 Reporter: Kihwal Lee Assignee: Robert Parker Attachments: HADOOP-9476-br0.23.patch HADOOP-9352 added a new test case testSetLoginUser. If it runs prior to other test cases, some of them fail. -- 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-9652) RawLocalFs#getFileLinkStatus does not fill in the link owner and mode
[
https://issues.apache.org/jira/browse/HADOOP-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723780#comment-13723780
]
Robert Parker commented on HADOOP-9652:
---
[~cnauroth] Please revert branch-2 also. All the test that I reported were
failing on branch-2.
RawLocalFs#getFileLinkStatus does not fill in the link owner and mode
-
Key: HADOOP-9652
URL: https://issues.apache.org/jira/browse/HADOOP-9652
Project: Hadoop Common
Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Andrew Wang
Fix For: 2.3.0
Attachments: hadoop-9452-1.patch, hadoop-9652-2.patch,
hadoop-9652-3.patch
{{RawLocalFs#getFileLinkStatus}} does not actually get the owner and mode of
the symlink, but instead uses the owner and mode of the symlink target. If
the target can't be found, it fills in bogus values (the empty string and
FsPermission.getDefault) for these.
Symlinks have an owner distinct from the owner of the target they point to,
and getFileLinkStatus ought to expose this.
In some operating systems, symlinks can have a permission other than 0777.
We ought to expose this in RawLocalFilesystem and other places, although we
don't necessarily have to support this behavior in HDFS.
--
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-9652) RawLocalFs#getFileLinkStatus does not fill in the link owner and mode
[
https://issues.apache.org/jira/browse/HADOOP-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723041#comment-13723041
]
Robert Parker commented on HADOOP-9652:
---
It appears to have also broken TestDFSShell#testCount, TestDFSShell#testText,
and TestDFSShell#testFilePermissions. Checked out the checkin just prior
(git:700817) and these test passed.
RawLocalFs#getFileLinkStatus does not fill in the link owner and mode
-
Key: HADOOP-9652
URL: https://issues.apache.org/jira/browse/HADOOP-9652
Project: Hadoop Common
Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Andrew Wang
Fix For: 2.3.0
Attachments: hadoop-9452-1.patch, hadoop-9652-2.patch,
hadoop-9652-3.patch
{{RawLocalFs#getFileLinkStatus}} does not actually get the owner and mode of
the symlink, but instead uses the owner and mode of the symlink target. If
the target can't be found, it fills in bogus values (the empty string and
FsPermission.getDefault) for these.
Symlinks have an owner distinct from the owner of the target they point to,
and getFileLinkStatus ought to expose this.
In some operating systems, symlinks can have a permission other than 0777.
We ought to expose this in RawLocalFilesystem and other places, although we
don't necessarily have to support this behavior in HDFS.
--
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-9652) RawLocalFs#getFileLinkStatus does not fill in the link owner and mode
[
https://issues.apache.org/jira/browse/HADOOP-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723070#comment-13723070
]
Robert Parker commented on HADOOP-9652:
---
Also breaks TestHttpFSFileSystemLocalFileSystem#testOperationDoAs and
TestHttpFSFileSystemLocalFileSystem#testOperation. Concur that we should
consider reverting.
RawLocalFs#getFileLinkStatus does not fill in the link owner and mode
-
Key: HADOOP-9652
URL: https://issues.apache.org/jira/browse/HADOOP-9652
Project: Hadoop Common
Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Andrew Wang
Fix For: 2.3.0
Attachments: hadoop-9452-1.patch, hadoop-9652-2.patch,
hadoop-9652-3.patch
{{RawLocalFs#getFileLinkStatus}} does not actually get the owner and mode of
the symlink, but instead uses the owner and mode of the symlink target. If
the target can't be found, it fills in bogus values (the empty string and
FsPermission.getDefault) for these.
Symlinks have an owner distinct from the owner of the target they point to,
and getFileLinkStatus ought to expose this.
In some operating systems, symlinks can have a permission other than 0777.
We ought to expose this in RawLocalFilesystem and other places, although we
don't necessarily have to support this behavior in HDFS.
--
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-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9752: -- Summary: Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid (was: Latest Ubuntu (13.10) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- 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-9752) Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13717876#comment-13717876 ] Robert Parker commented on HADOOP-9752: --- [~j...@nanthrax.net] can you please try /bin/kill. kill is usually a built-in shell command and the built in command for Ubuntu works for me too (zsh and bash). Additionally can you check /bin/kill --version. Mine is 'kill from procps-ng 3.3.3'. Latest Ubuntu (13.04) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- 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-9752) Latest Ubuntu (13.10) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid
[ https://issues.apache.org/jira/browse/HADOOP-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9752: -- Summary: Latest Ubuntu (13.10) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid (was: Latest Ubuntu (13.10) /bin/kill parameter for process group requires a 'double dash kill -0 --pid) Latest Ubuntu (13.10) /bin/kill parameter for process group requires a 'double dash kill -0 -- -pid -- Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Robert Parker This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- 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-9752) Latest Ubuntu (13.10) /bin/kill parameter for process group requires a 'double dash kill -0 --pid
Robert Parker created HADOOP-9752: - Summary: Latest Ubuntu (13.10) /bin/kill parameter for process group requires a 'double dash kill -0 --pid Key: HADOOP-9752 URL: https://issues.apache.org/jira/browse/HADOOP-9752 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 2.0.4-alpha, 3.0.0 Reporter: Robert Parker This changed on Ubuntu 12.10 and later. This prevents the kill command from executing correctly in Shell.java. There is a bug filed in Ubuntu but there is not much activity. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1077796 -- 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-9317) User cannot specify a kerberos keytab for commands
[
https://issues.apache.org/jira/browse/HADOOP-9317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Parker updated HADOOP-9317:
--
Attachment: HADOOP-9317.patch
Refreshed the patch to latest trunk/branch-2
User cannot specify a kerberos keytab for commands
--
Key: HADOOP-9317
URL: https://issues.apache.org/jira/browse/HADOOP-9317
Project: Hadoop Common
Issue Type: Bug
Components: security
Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Priority: Critical
Attachments: HADOOP-9317.branch-23.patch,
HADOOP-9317.branch-23.patch, HADOOP-9317.patch, HADOOP-9317.patch,
HADOOP-9317.patch, HADOOP-9317.patch
{{UserGroupInformation}} only allows kerberos users to be logged in via the
ticket cache when running hadoop commands. {{UGI}} allows a keytab to be
used, but it's only exposed programatically. This forces keytab-based users
running hadoop commands to periodically issue a kinit from the keytab. A
race condition exists during the kinit when the ticket cache is deleted and
re-created. Hadoop commands will fail when the ticket cache does not
momentarily exist.
--
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-9469) mapreduce/yarn source jars not included in dist tarball
[ https://issues.apache.org/jira/browse/HADOOP-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9469: -- Attachment: HADOOP-9469-branch-2.patch HADOOP-9469-branch-0.23.patch mapreduce/yarn source jars not included in dist tarball --- Key: HADOOP-9469 URL: https://issues.apache.org/jira/browse/HADOOP-9469 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.0 Reporter: Thomas Graves Assignee: Robert Parker Attachments: HADOOP-9469-branch-0.23.patch, HADOOP-9469-branch-2.patch, HADOOP-9469.patch, HADOOP-9469.patch the mapreduce and yarn sources jars don't get included into the distribution tarball. It seems they get built by default just aren't assembled. -- 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-9469) mapreduce/yarn source jars not included in dist tarball
[ https://issues.apache.org/jira/browse/HADOOP-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9469: -- Attachment: HADOOP-9469.patch mapreduce/yarn source jars not included in dist tarball --- Key: HADOOP-9469 URL: https://issues.apache.org/jira/browse/HADOOP-9469 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.0 Reporter: Thomas Graves Assignee: Robert Parker Attachments: HADOOP-9469.patch, HADOOP-9469.patch the mapreduce and yarn sources jars don't get included into the distribution tarball. It seems they get built by default just aren't assembled. -- 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-9469) mapreduce/yarn source jars not included in dist tarball
[ https://issues.apache.org/jira/browse/HADOOP-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13630443#comment-13630443 ] Robert Parker commented on HADOOP-9469: --- Added sources for hadoop-tools and corrected mapreduce sources that were omitted. mapreduce/yarn source jars not included in dist tarball --- Key: HADOOP-9469 URL: https://issues.apache.org/jira/browse/HADOOP-9469 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.0 Reporter: Thomas Graves Assignee: Robert Parker Attachments: HADOOP-9469.patch, HADOOP-9469.patch the mapreduce and yarn sources jars don't get included into the distribution tarball. It seems they get built by default just aren't assembled. -- 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] [Moved] (HADOOP-9469) mapreduce/yarn source jars not included in dist tarball
[ https://issues.apache.org/jira/browse/HADOOP-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker moved MAPREDUCE-3707 to HADOOP-9469: -- Component/s: (was: mrv2) Target Version/s: 3.0.0, 0.23.7, 2.0.5-beta (was: 0.23.3, 2.0.0-alpha, 3.0.0) Affects Version/s: (was: 0.23.0) 0.23.0 Key: HADOOP-9469 (was: MAPREDUCE-3707) Project: Hadoop Common (was: Hadoop Map/Reduce) mapreduce/yarn source jars not included in dist tarball --- Key: HADOOP-9469 URL: https://issues.apache.org/jira/browse/HADOOP-9469 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.0 Reporter: Thomas Graves the mapreduce and yarn sources jars don't get included into the distribution tarball. It seems they get built by default just aren't assembled. -- 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-9469) mapreduce/yarn source jars not included in dist tarball
[ https://issues.apache.org/jira/browse/HADOOP-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9469: -- Assignee: Robert Parker mapreduce/yarn source jars not included in dist tarball --- Key: HADOOP-9469 URL: https://issues.apache.org/jira/browse/HADOOP-9469 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.0 Reporter: Thomas Graves Assignee: Robert Parker the mapreduce and yarn sources jars don't get included into the distribution tarball. It seems they get built by default just aren't assembled. -- 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-9469) mapreduce/yarn source jars not included in dist tarball
[ https://issues.apache.org/jira/browse/HADOOP-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9469: -- Attachment: HADOOP-9469.patch After change: tar tvf ./hadoop-dist/target/hadoop-3.0.0-SNAPSHOT.tar.gz | grep sources.jar -rw-r--r-- 0 rparker staff 361204 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-api-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff 18468 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-applications-distributedshell-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff4148 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-applications-distributedshell-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff5815 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-applications-unmanaged-am-launcher-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff3839 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-applications-unmanaged-am-launcher-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 23560 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-client-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff 12185 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-client-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 511146 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-common-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff 77299 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-common-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 54051 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-server-common-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff7737 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-server-common-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 246997 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-server-nodemanager-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff 135604 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-server-nodemanager-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 334917 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-server-resourcemanager-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff 192273 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-server-resourcemanager-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 17612 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-server-tests-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 17281 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-server-web-proxy-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff4916 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/yarn/sources/hadoop-yarn-server-web-proxy-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 227933 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-client-common-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff 23255 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-client-common-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 947984 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-client-core-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff 55819 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-client-core-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 71566 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-client-hs-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff 61378 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-client-hs-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 19997 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-client-jobclient-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff 84 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-client-jobclient-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 10309 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-client-shuffle-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff4026 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-client-shuffle-3.0.0-SNAPSHOT-test-sources.jar -rw-r--r-- 0 rparker staff 696883 Apr 10 15:18 hadoop-3.0.0-SNAPSHOT/share/hadoop/mapreduce/sources/hadoop-mapreduce-examples-3.0.0-SNAPSHOT-sources.jar -rw-r--r-- 0 rparker staff 12968 Apr 10 15:18
[jira] [Updated] (HADOOP-9469) mapreduce/yarn source jars not included in dist tarball
[ https://issues.apache.org/jira/browse/HADOOP-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9469: -- Status: Patch Available (was: Open) mapreduce/yarn source jars not included in dist tarball --- Key: HADOOP-9469 URL: https://issues.apache.org/jira/browse/HADOOP-9469 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.0 Reporter: Thomas Graves Assignee: Robert Parker Attachments: HADOOP-9469.patch the mapreduce and yarn sources jars don't get included into the distribution tarball. It seems they get built by default just aren't assembled. -- 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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13554406#comment-13554406 ] Robert Parker commented on HADOOP-9106: --- Suresh with resect to | Change final public static to public static final I would like to leave final public static for consistency and file a separate ticket to change all the uses of final public static to public static final. Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch, HADOOP-9106v2.patch, HADOOP-9106v3.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9106: -- Attachment: HADOOP-9106v4.patch Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch, HADOOP-9106v2.patch, HADOOP-9106v3.patch, HADOOP-9106v4.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13554480#comment-13554480 ] Robert Parker commented on HADOOP-9106: --- Suresh, Thanks for your input. This patch uses the correct convention and has the final member variable. Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch, HADOOP-9106v2.patch, HADOOP-9106v3.patch, HADOOP-9106v4.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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] [Assigned] (HADOOP-9193) hadoop script can inadvertently expand wildcard arguments when delegating to hdfs script
[
https://issues.apache.org/jira/browse/HADOOP-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Parker reassigned HADOOP-9193:
-
Assignee: Robert Parker
hadoop script can inadvertently expand wildcard arguments when delegating to
hdfs script
Key: HADOOP-9193
URL: https://issues.apache.org/jira/browse/HADOOP-9193
Project: Hadoop Common
Issue Type: Bug
Components: scripts
Affects Versions: 2.0.2-alpha, 0.23.5
Reporter: Jason Lowe
Assignee: Robert Parker
Priority: Minor
The hadoop front-end script will print a deprecation warning and defer to the
hdfs front-end script for certain commands, like fsck, dfs. If a wildcard
appears as an argument then it can be inadvertently expanded by the shell to
match a local filesystem path before being sent to the hdfs script, which can
be very confusing to the end user.
For example, the following two commands usually perform very different
things, even though they should be equivalent:
{code}
hadoop fs -ls /tmp/\*
hadoop dfs -ls /tmp/\*
{code}
The former lists everything in the default filesystem under /tmp, while the
latter expands /tmp/\* into everything in the *local* filesystem under /tmp
and passes those as arguments to try to list in the default filesystem.
--
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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9106: -- Attachment: HADOOP-9106v3.patch Made the set and get static and did not use a member variable to match the same pattern in Client for setPingInterval and getPingInterval functions. Added the default to the core-default.xml Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch, HADOOP-9106v2.patch, HADOOP-9106v3.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547113#comment-13547113 ] Robert Parker commented on HADOOP-9106: --- Suresh, using a class member variable would require it to be set only once in the constructor unless we make the setter function non-static. The passing of the conf in the setter makes the use of static desirable but the setting of a member variable makes it undesirable, I chose the static option since the connections are cached and so there is not a lot of time spent trying to establish the connection. We could set the member variable in the constructor but that dilutes the meaning of setTimeoutConnection (even if it may not actual use case to set it more than once). Bottom line I thought this way was the cleanest implementation. If you still think the member variable is required please let me know if you want to set it once in the constructor or remove the static qualifier from the function. Thanks for reviewing the patch, Rob Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch, HADOOP-9106v2.patch, HADOOP-9106v3.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9106: -- Attachment: HADOOP-9106v1.patch Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9106: -- Status: Patch Available (was: Open) Made the timeout parameter configurable and set-able. Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9106: -- Status: Open (was: Patch Available) Need to correct the unit test Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9106: -- Attachment: HADOOP-9106v2.patch Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch, HADOOP-9106v2.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9106: -- Status: Patch Available (was: Open) Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch, HADOOP-9106v2.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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-9106) Allow configuration of IPC connect timeout
[ https://issues.apache.org/jira/browse/HADOOP-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13544337#comment-13544337 ] Robert Parker commented on HADOOP-9106: --- Suresh, I think making setConnectionTimeout static will not allow configuring 'per-client' which is desired. Concur with replacing the getConnectionTimeout. Allow configuration of IPC connect timeout -- Key: HADOOP-9106 URL: https://issues.apache.org/jira/browse/HADOOP-9106 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 3.0.0 Reporter: Todd Lipcon Assignee: Robert Parker Attachments: HADOOP-9106v1.patch, HADOOP-9106v2.patch Currently the connection timeout in Client.setupConnection() is hard coded to 20seconds. This is unreasonable in some scenarios, such as HA failover, if we want a faster failover time. We should allow this to be configured per-client. -- 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-9120) Modify Security Conditional that check for KERBEROS
[ https://issues.apache.org/jira/browse/HADOOP-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9120: -- Issue Type: New Feature (was: Sub-task) Parent: (was: HADOOP-8779) Modify Security Conditional that check for KERBEROS --- Key: HADOOP-9120 URL: https://issues.apache.org/jira/browse/HADOOP-9120 Project: Hadoop Common Issue Type: New Feature Components: fs, security Reporter: Robert Parker Assignee: Robert Parker To support PLAIN authentication, checks should disallow certain types (TOKEN for token delegation) instead of allowing only KERBEROS -- 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-9072) Hadoop-Common-0.23-Build Fails to build in Jenkins
[ https://issues.apache.org/jira/browse/HADOOP-9072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9072: -- Status: Patch Available (was: Open) Hadoop-Common-0.23-Build Fails to build in Jenkins -- Key: HADOOP-9072 URL: https://issues.apache.org/jira/browse/HADOOP-9072 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.4 Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9072.patch [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile (default-testCompile) on project hadoop-common: Compilation failure: Compilation failure: [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/clover/src-test-instrumented/org/apache/hadoop/record/RecInt.java:[4,7] duplicate class: org.apache.hadoop.record.RecInt [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/generated-test-sources/java/org/apache/hadoop/record/RecRecordOld.java:[4,7] duplicate class: org.apache.hadoop.record.RecRecordOld [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/clover/src-test-instrumented/org/apache/hadoop/record/RecString.java:[4,7] duplicate class: org.apache.hadoop.record.RecString [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/generated-test-sources/java/org/apache/hadoop/record/RecBuffer.java:[4,7] duplicate class: org.apache.hadoop.record.RecBuffer [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/clover/src-test-instrumented/org/apache/hadoop/record/RecRecord1.java:[4,7] duplicate class: org.apache.hadoop.record.RecRecord1 [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/clover/src-test-instrumented/org/apache/hadoop/record/RecRecordNew.java:[4,7] duplicate class: org.apache.hadoop.record.RecRecordNew [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/clover/src-test-instrumented/org/apache/hadoop/record/RecRecord0.java:[4,7] duplicate class: org.apache.hadoop.record.RecRecord0 -- 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-9072) Hadoop-Common-0.23-Build Fails to build in Jenkins
[ https://issues.apache.org/jira/browse/HADOOP-9072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-9072: -- Attachment: HADOOP-9072.patch Hadoop-Common-0.23-Build Fails to build in Jenkins -- Key: HADOOP-9072 URL: https://issues.apache.org/jira/browse/HADOOP-9072 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.4 Reporter: Robert Parker Assignee: Robert Parker Attachments: HADOOP-9072.patch [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile (default-testCompile) on project hadoop-common: Compilation failure: Compilation failure: [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/clover/src-test-instrumented/org/apache/hadoop/record/RecInt.java:[4,7] duplicate class: org.apache.hadoop.record.RecInt [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/generated-test-sources/java/org/apache/hadoop/record/RecRecordOld.java:[4,7] duplicate class: org.apache.hadoop.record.RecRecordOld [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/clover/src-test-instrumented/org/apache/hadoop/record/RecString.java:[4,7] duplicate class: org.apache.hadoop.record.RecString [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/generated-test-sources/java/org/apache/hadoop/record/RecBuffer.java:[4,7] duplicate class: org.apache.hadoop.record.RecBuffer [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/clover/src-test-instrumented/org/apache/hadoop/record/RecRecord1.java:[4,7] duplicate class: org.apache.hadoop.record.RecRecord1 [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/clover/src-test-instrumented/org/apache/hadoop/record/RecRecordNew.java:[4,7] duplicate class: org.apache.hadoop.record.RecRecordNew [ERROR] /home/jenkins/jenkins-slave/workspace/Hadoop-Common-0.23-Build/trunk/hadoop-common-project/hadoop-common/target/clover/src-test-instrumented/org/apache/hadoop/record/RecRecord0.java:[4,7] duplicate class: org.apache.hadoop.record.RecRecord0 -- 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-8987) TestLocalMRNotification.testMR failed in Hudson
Robert Parker created HADOOP-8987: - Summary: TestLocalMRNotification.testMR failed in Hudson Key: HADOOP-8987 URL: https://issues.apache.org/jira/browse/HADOOP-8987 Project: Hadoop Common Issue Type: Bug Components: test Reporter: Robert Parker TestLocalMRNotification.testMR failed in Hudson, from [build #3911|http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3911/testReport/] to the latest, [build #3917|http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3917/testReport/]. -- 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-8987) TestLocalMRNotification.testMR failed in Hudson
[ https://issues.apache.org/jira/browse/HADOOP-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13485288#comment-13485288 ] Robert Parker commented on HADOOP-8987: --- Builds https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2968/ and https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2966/ fail on this unit test in Hudson. Applying the patch to trunk locally does not fail that test. TestLocalMRNotification.testMR failed in Hudson --- Key: HADOOP-8987 URL: https://issues.apache.org/jira/browse/HADOOP-8987 Project: Hadoop Common Issue Type: Bug Components: test Reporter: Robert Parker TestLocalMRNotification.testMR failed in Hudson, from [build #3911|http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3911/testReport/] to the latest, [build #3917|http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3917/testReport/]. -- 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-8906) paths with multiple globs are unreliable
[ https://issues.apache.org/jira/browse/HADOOP-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8906: -- Attachment: HADOOP-8906-branch_0.23.patch patch for branch 0.23 paths with multiple globs are unreliable Key: HADOOP-8906 URL: https://issues.apache.org/jira/browse/HADOOP-8906 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0 Reporter: Daryn Sharp Assignee: Daryn Sharp Priority: Critical Attachments: HADOOP-8906-branch_0.23.patch, HADOOP-8906.patch, HADOOP-8906.patch, HADOOP-8906.patch, HADOOP-8906.patch, HADOOP-8906.patch Let's say we have have a structure of $date/$user/stuff/file. Multiple globs are unreliable unless every directory in the structure exists. These work: date*/user date*/user/stuff date*/user/stuff/file These fail: date*/user/* date*/user/*/* date*/user/stu* date*/user/stu*/* date*/user/stu*/file date*/user/stuff/* date*/user/stuff/f* -- 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-8712) Change default hadoop.security.group.mapping
[ https://issues.apache.org/jira/browse/HADOOP-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8712: -- Attachment: HADOOP-8712-v2.patch Corrected spelling error, explicitly stated the fallback mechanism, moved the description to core-default.xml with a reference in the hdfs-permission-guide.xml to eliminate multiple maintenance points. Change default hadoop.security.group.mapping Key: HADOOP-8712 URL: https://issues.apache.org/jira/browse/HADOOP-8712 Project: Hadoop Common Issue Type: Improvement Components: security Affects Versions: 2.2.0-alpha Reporter: Robert Parker Assignee: Robert Parker Priority: Minor Attachments: HADOOP-8712-v1.patch, HADOOP-8712-v2.patch Change the hadoop.security.group.mapping in core-site to JniBasedUnixGroupsNetgroupMappingWithFallback -- 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-8712) Change default hadoop.security.group.mapping
[ https://issues.apache.org/jira/browse/HADOOP-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8712: -- Affects Version/s: (was: 0.23.3) Change default hadoop.security.group.mapping Key: HADOOP-8712 URL: https://issues.apache.org/jira/browse/HADOOP-8712 Project: Hadoop Common Issue Type: Improvement Components: security Affects Versions: 2.2.0-alpha Reporter: Robert Parker Assignee: Robert Parker Priority: Minor Change the hadoop.security.group.mapping in core-site to JniBasedUnixGroupsNetgroupMappingWithFallback -- 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-8712) Change default hadoop.security.group.mapping
[ https://issues.apache.org/jira/browse/HADOOP-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8712: -- Affects Version/s: (was: 2.0.0-alpha) 2.2.0-alpha Change default hadoop.security.group.mapping Key: HADOOP-8712 URL: https://issues.apache.org/jira/browse/HADOOP-8712 Project: Hadoop Common Issue Type: Improvement Components: security Affects Versions: 2.2.0-alpha Reporter: Robert Parker Assignee: Robert Parker Priority: Minor Change the hadoop.security.group.mapping in core-site to JniBasedUnixGroupsNetgroupMappingWithFallback -- 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-8712) Change default hadoop.security.group.mapping
[ https://issues.apache.org/jira/browse/HADOOP-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8712: -- Attachment: HADOOP-8712-v1.patch Changed the default to JniBasedUnixGroupsMappingWithFallback. Updated the documentation. Change default hadoop.security.group.mapping Key: HADOOP-8712 URL: https://issues.apache.org/jira/browse/HADOOP-8712 Project: Hadoop Common Issue Type: Improvement Components: security Affects Versions: 2.2.0-alpha Reporter: Robert Parker Assignee: Robert Parker Priority: Minor Attachments: HADOOP-8712-v1.patch Change the hadoop.security.group.mapping in core-site to JniBasedUnixGroupsNetgroupMappingWithFallback -- 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-8712) Change default hadoop.security.group.mapping
[ https://issues.apache.org/jira/browse/HADOOP-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8712: -- Status: Patch Available (was: Open) Change default hadoop.security.group.mapping Key: HADOOP-8712 URL: https://issues.apache.org/jira/browse/HADOOP-8712 Project: Hadoop Common Issue Type: Improvement Components: security Affects Versions: 2.2.0-alpha Reporter: Robert Parker Assignee: Robert Parker Priority: Minor Attachments: HADOOP-8712-v1.patch Change the hadoop.security.group.mapping in core-site to JniBasedUnixGroupsNetgroupMappingWithFallback -- 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-8712) Change default hadoop.security.group.mapping
[ https://issues.apache.org/jira/browse/HADOOP-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440650#comment-13440650 ] Robert Parker commented on HADOOP-8712: --- HDFS-3837 and HDFS-3850 addresses the findbugs issues Change default hadoop.security.group.mapping Key: HADOOP-8712 URL: https://issues.apache.org/jira/browse/HADOOP-8712 Project: Hadoop Common Issue Type: Improvement Components: security Affects Versions: 2.2.0-alpha Reporter: Robert Parker Assignee: Robert Parker Priority: Minor Attachments: HADOOP-8712-v1.patch Change the hadoop.security.group.mapping in core-site to JniBasedUnixGroupsNetgroupMappingWithFallback -- 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-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8611: -- Attachment: HADOOP-8611-branch1.patch removed mvn references Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails -- Key: HADOOP-8611 URL: https://issues.apache.org/jira/browse/HADOOP-8611 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha Reporter: Kihwal Lee Assignee: Robert Parker Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha Attachments: HADOOP-8611-branch1.patch, HADOOP-8611-branch1.patch, HADOOP-8611.patch, HADOOP-8611.patch When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being disabled. -- 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-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8611: -- Attachment: HADOOP-8611.patch added curly braces Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails -- Key: HADOOP-8611 URL: https://issues.apache.org/jira/browse/HADOOP-8611 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha Reporter: Kihwal Lee Assignee: Robert Parker Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha Attachments: HADOOP-8611-branch1.patch, HADOOP-8611-branch1.patch, HADOOP-8611.patch, HADOOP-8611.patch, HADOOP-8611.patch When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being disabled. -- 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-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13438189#comment-13438189 ] Robert Parker commented on HADOOP-8611: --- added a new patch for branch 1 to remove mvn references and added curly braces to if statement added a new patch for trunk to add curly braces to if statement Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails -- Key: HADOOP-8611 URL: https://issues.apache.org/jira/browse/HADOOP-8611 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha Reporter: Kihwal Lee Assignee: Robert Parker Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha Attachments: HADOOP-8611-branch1.patch, HADOOP-8611-branch1.patch, HADOOP-8611.patch, HADOOP-8611.patch, HADOOP-8611.patch When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being disabled. -- 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-8712) Change default hadoop.security.group.mapping
Robert Parker created HADOOP-8712: - Summary: Change default hadoop.security.group.mapping Key: HADOOP-8712 URL: https://issues.apache.org/jira/browse/HADOOP-8712 Project: Hadoop Common Issue Type: Improvement Components: security Affects Versions: 2.0.0-alpha, 0.23.3 Reporter: Robert Parker Assignee: Robert Parker Priority: Minor Change the hadoop.security.group.mapping in core-site to JniBasedUnixGroupsNetgroupMappingWithFallback -- 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-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8611: -- Attachment: HADOOP-8611.patch Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails -- Key: HADOOP-8611 URL: https://issues.apache.org/jira/browse/HADOOP-8611 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha Reporter: Kihwal Lee Assignee: Robert Parker Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha Attachments: HADOOP-8611.patch, HADOOP-8611.patch When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being disabled. -- 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-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13436028#comment-13436028 ] Robert Parker commented on HADOOP-8611: --- Uploaded new patch, isolated the fallback functionality to 2 new specific classes which can be specified within the current configuration scheme. Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails -- Key: HADOOP-8611 URL: https://issues.apache.org/jira/browse/HADOOP-8611 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha Reporter: Kihwal Lee Assignee: Robert Parker Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha Attachments: HADOOP-8611.patch, HADOOP-8611.patch When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being disabled. -- 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-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8611: -- Attachment: HADOOP-8611-branch1.patch Patch for branch-1.0.2 Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails -- Key: HADOOP-8611 URL: https://issues.apache.org/jira/browse/HADOOP-8611 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha Reporter: Kihwal Lee Assignee: Robert Parker Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha Attachments: HADOOP-8611-branch1.patch, HADOOP-8611.patch, HADOOP-8611.patch When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being disabled. -- 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-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8611: -- Attachment: HADOOP-8611.patch Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails -- Key: HADOOP-8611 URL: https://issues.apache.org/jira/browse/HADOOP-8611 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha Reporter: Kihwal Lee Assignee: Robert Parker Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha Attachments: HADOOP-8611.patch When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being disabled. -- 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-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated HADOOP-8611: -- Target Version/s: 0.23.3, 2.1.0-alpha Status: Patch Available (was: Open) This patch applies to trunk. Once reviewed I will post the 1.0 patch Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails -- Key: HADOOP-8611 URL: https://issues.apache.org/jira/browse/HADOOP-8611 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 2.0.0-alpha, 0.23.0, 1.0.3 Reporter: Kihwal Lee Assignee: Robert Parker Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha Attachments: HADOOP-8611.patch When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being disabled. -- 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-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435181#comment-13435181 ] Robert Parker commented on HADOOP-8611: --- core-tests failures were time out issues, verified locally on trunk and my branch that TestZKFailoverController tests pass. Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails -- Key: HADOOP-8611 URL: https://issues.apache.org/jira/browse/HADOOP-8611 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha Reporter: Kihwal Lee Assignee: Robert Parker Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha Attachments: HADOOP-8611.patch When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being disabled. -- 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] [Assigned] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker reassigned HADOOP-8611: - Assignee: Robert Parker (was: Kihwal Lee) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails -- Key: HADOOP-8611 URL: https://issues.apache.org/jira/browse/HADOOP-8611 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha Reporter: Kihwal Lee Assignee: Robert Parker Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being disabled. -- 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
