[jira] [Updated] (HADOOP-9450) HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of APpended
[
https://issues.apache.org/jira/browse/HADOOP-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-9450:
--
Attachment: HADOOP-9450-branch-1.patch
HADOOP-9450-branch-1-win.patch
Hi, Harsh. I hope you don't mind, but I went ahead and back-ported your trunk
patch to branch-1 and branch-1-win. I tested these on Mac and Windows.
HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of
APpended
--
Key: HADOOP-9450
URL: https://issues.apache.org/jira/browse/HADOOP-9450
Project: Hadoop Common
Issue Type: Bug
Reporter: Mitch Wyle
Attachments: HADOOP-9450-branch-1.patch,
HADOOP-9450-branch-1-win.patch, HADOOP-9450.patch
On line 133 of the hadoop shell wrapper, CLASSPATH is set as:
CLASSPATH=${CLASSPATH}:${HADOOP_CLASSPATH}
Notice that the built-up CLASSPATH, along with all the libs and unwanted JARS
are pre-pended BEFORE the user's HADOOP_CLASSPATH. Therefore there is no way
to put your own JARs in front of those that the hadoop wrapper script sets.
We propose a patch that reverses this order. Failing that, we would like to
add a command line option to override this behavior and enable a user's JARs
to be found before the wrong ones in the Hadoop library paths.
We always welcome your opinions.
--
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-9450) HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of APpended
[
https://issues.apache.org/jira/browse/HADOOP-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-9450:
--
Attachment: HADOOP-9450.patch
Re-uploading Harsh's trunk patch, just so Jenkins sees it as the latest
attachment.
HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of
APpended
--
Key: HADOOP-9450
URL: https://issues.apache.org/jira/browse/HADOOP-9450
Project: Hadoop Common
Issue Type: Bug
Reporter: Mitch Wyle
Attachments: HADOOP-9450-branch-1.patch,
HADOOP-9450-branch-1-win.patch, HADOOP-9450.patch, HADOOP-9450.patch
On line 133 of the hadoop shell wrapper, CLASSPATH is set as:
CLASSPATH=${CLASSPATH}:${HADOOP_CLASSPATH}
Notice that the built-up CLASSPATH, along with all the libs and unwanted JARS
are pre-pended BEFORE the user's HADOOP_CLASSPATH. Therefore there is no way
to put your own JARs in front of those that the hadoop wrapper script sets.
We propose a patch that reverses this order. Failing that, we would like to
add a command line option to override this behavior and enable a user's JARs
to be found before the wrong ones in the Hadoop library paths.
We always welcome your opinions.
--
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-9450) HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of APpended
[
https://issues.apache.org/jira/browse/HADOOP-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-9450:
--
Status: Patch Available (was: Open)
HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of
APpended
--
Key: HADOOP-9450
URL: https://issues.apache.org/jira/browse/HADOOP-9450
Project: Hadoop Common
Issue Type: Bug
Reporter: Mitch Wyle
Attachments: HADOOP-9450-branch-1.patch,
HADOOP-9450-branch-1-win.patch, HADOOP-9450.patch, HADOOP-9450.patch
On line 133 of the hadoop shell wrapper, CLASSPATH is set as:
CLASSPATH=${CLASSPATH}:${HADOOP_CLASSPATH}
Notice that the built-up CLASSPATH, along with all the libs and unwanted JARS
are pre-pended BEFORE the user's HADOOP_CLASSPATH. Therefore there is no way
to put your own JARs in front of those that the hadoop wrapper script sets.
We propose a patch that reverses this order. Failing that, we would like to
add a command line option to override this behavior and enable a user's JARs
to be found before the wrong ones in the Hadoop library paths.
We always welcome your opinions.
--
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-9450) HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of APpended
[
https://issues.apache.org/jira/browse/HADOOP-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632625#comment-13632625
]
Harsh J commented on HADOOP-9450:
-
No problem and thanks! Was gonna get to it later today but you've saved me the
work; I'll need to wait for a committer's approval here before I commit these
in since the trunk patch was from me (can't commit self patches prior).
+1 on the branch-{1,1-win} changes - will commit them after trunk gets a
go-ahead.
HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of
APpended
--
Key: HADOOP-9450
URL: https://issues.apache.org/jira/browse/HADOOP-9450
Project: Hadoop Common
Issue Type: Bug
Reporter: Mitch Wyle
Attachments: HADOOP-9450-branch-1.patch,
HADOOP-9450-branch-1-win.patch, HADOOP-9450.patch, HADOOP-9450.patch
On line 133 of the hadoop shell wrapper, CLASSPATH is set as:
CLASSPATH=${CLASSPATH}:${HADOOP_CLASSPATH}
Notice that the built-up CLASSPATH, along with all the libs and unwanted JARS
are pre-pended BEFORE the user's HADOOP_CLASSPATH. Therefore there is no way
to put your own JARs in front of those that the hadoop wrapper script sets.
We propose a patch that reverses this order. Failing that, we would like to
add a command line option to override this behavior and enable a user's JARs
to be found before the wrong ones in the Hadoop library paths.
We always welcome your opinions.
--
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-9287) Parallel testing hadoop-common
[
https://issues.apache.org/jira/browse/HADOOP-9287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632629#comment-13632629
]
Hadoop QA commented on HADOOP-9287:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12578866/HADOOP-9287--N5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 52 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs
hadoop-tools/hadoop-distcp
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2449//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2449//console
This message is automatically generated.
Parallel testing hadoop-common
--
Key: HADOOP-9287
URL: https://issues.apache.org/jira/browse/HADOOP-9287
Project: Hadoop Common
Issue Type: Test
Components: test
Affects Versions: 3.0.0
Reporter: Tsuyoshi OZAWA
Assignee: Andrey Klochkov
Attachments: HADOOP-9287.1.patch, HADOOP-9287--N3.patch,
HADOOP-9287--N3.patch, HADOOP-9287--N4.patch, HADOOP-9287--N5.patch,
HADOOP-9287.patch, HADOOP-9287.patch
The maven surefire plugin supports parallel testing feature. By using it, the
tests can be run more faster.
--
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-9450) HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of APpended
[
https://issues.apache.org/jira/browse/HADOOP-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632631#comment-13632631
]
Hadoop QA commented on HADOOP-9450:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12578883/HADOOP-9450.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2450//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2450//console
This message is automatically generated.
HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of
APpended
--
Key: HADOOP-9450
URL: https://issues.apache.org/jira/browse/HADOOP-9450
Project: Hadoop Common
Issue Type: Bug
Reporter: Mitch Wyle
Attachments: HADOOP-9450-branch-1.patch,
HADOOP-9450-branch-1-win.patch, HADOOP-9450.patch, HADOOP-9450.patch
On line 133 of the hadoop shell wrapper, CLASSPATH is set as:
CLASSPATH=${CLASSPATH}:${HADOOP_CLASSPATH}
Notice that the built-up CLASSPATH, along with all the libs and unwanted JARS
are pre-pended BEFORE the user's HADOOP_CLASSPATH. Therefore there is no way
to put your own JARs in front of those that the hadoop wrapper script sets.
We propose a patch that reverses this order. Failing that, we would like to
add a command line option to override this behavior and enable a user's JARs
to be found before the wrong ones in the Hadoop library paths.
We always welcome your opinions.
--
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-9450) HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of APpended
[
https://issues.apache.org/jira/browse/HADOOP-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632637#comment-13632637
]
Harsh J commented on HADOOP-9450:
-
{quote}
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{quote}
Patch changes the script; no existing tests are present. Patch was tested by
running in the shell's debug mode (bash -x) for Linux by me to observe
difference in built CLASSPATH based on the HADOOP_USER_CLASSPATH_FIRST toggle
and was also verified by Chris for behavior on Windows manually.
HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of
APpended
--
Key: HADOOP-9450
URL: https://issues.apache.org/jira/browse/HADOOP-9450
Project: Hadoop Common
Issue Type: Bug
Reporter: Mitch Wyle
Attachments: HADOOP-9450-branch-1.patch,
HADOOP-9450-branch-1-win.patch, HADOOP-9450.patch, HADOOP-9450.patch
On line 133 of the hadoop shell wrapper, CLASSPATH is set as:
CLASSPATH=${CLASSPATH}:${HADOOP_CLASSPATH}
Notice that the built-up CLASSPATH, along with all the libs and unwanted JARS
are pre-pended BEFORE the user's HADOOP_CLASSPATH. Therefore there is no way
to put your own JARs in front of those that the hadoop wrapper script sets.
We propose a patch that reverses this order. Failing that, we would like to
add a command line option to override this behavior and enable a user's JARs
to be found before the wrong ones in the Hadoop library paths.
We always welcome your opinions.
--
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-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632988#comment-13632988
]
Hadoop QA commented on HADOOP-9455:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12578954/HADOOP-9455.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2451//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2451//console
This message is automatically generated.
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Sangjin Lee
Assignee: Chris Nauroth
Priority: Minor
Attachments: HADOOP-9455.1.patch, HADOOP-9455.2.patch
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
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-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632998#comment-13632998
]
Chris Nauroth commented on HADOOP-9455:
---
{quote}
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{quote}
No tests, because this is a change in scripting only. I built distribution
tarballs on both Mac and Windows and tested using HADOOP_CLIENT_OPTS to specify
the remote debugging options that Sangjin used in the bug report.
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Sangjin Lee
Assignee: Chris Nauroth
Priority: Minor
Attachments: HADOOP-9455.1.patch, HADOOP-9455.2.patch
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
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-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633036#comment-13633036
]
Arpit Agarwal commented on HADOOP-9455:
---
+1
Thanks Chris.
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Sangjin Lee
Assignee: Chris Nauroth
Priority: Minor
Attachments: HADOOP-9455.1.patch, HADOOP-9455.2.patch
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
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-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633044#comment-13633044
]
Sangjin Lee commented on HADOOP-9455:
-
+1. Thanks!
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Sangjin Lee
Assignee: Chris Nauroth
Priority: Minor
Attachments: HADOOP-9455.1.patch, HADOOP-9455.2.patch
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
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] [Reopened] (HADOOP-9473) typo in FileUtil copy() method
[
https://issues.apache.org/jira/browse/HADOOP-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao reopened HADOOP-9473:
---
We also needs to fix the same typo in testConf.xml accordingly. Otherwise
TestCLI will fail.
typo in FileUtil copy() method
--
Key: HADOOP-9473
URL: https://issues.apache.org/jira/browse/HADOOP-9473
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 2.0.0-alpha, 1.1.2
Reporter: Glen Mazza
Priority: Trivial
Fix For: 1.2.0, 2.0.5-beta
Attachments: HADOOP-9473.branch-1.patch, HADOOP-9473.patch
typo:
{code}
Index: src/core/org/apache/hadoop/fs/FileUtil.java
===
--- src/core/org/apache/hadoop/fs/FileUtil.java (revision 1467295)
+++ src/core/org/apache/hadoop/fs/FileUtil.java (working copy)
@@ -178,7 +178,7 @@
// Check if dest is directory
if (!dstFS.exists(dst)) {
throw new IOException(` + dst +': specified destination directory
+
-doest not exist);
+does not exist);
} else {
FileStatus sdst = dstFS.getFileStatus(dst);
if (!sdst.isDir())
{code}
--
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-9473) typo in FileUtil copy() method
[
https://issues.apache.org/jira/browse/HADOOP-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HADOOP-9473:
--
Attachment: HADOOP-9473.patch
The patch for branch-1.2.
typo in FileUtil copy() method
--
Key: HADOOP-9473
URL: https://issues.apache.org/jira/browse/HADOOP-9473
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 2.0.0-alpha, 1.1.2
Reporter: Glen Mazza
Priority: Trivial
Fix For: 1.2.0, 2.0.5-beta
Attachments: HADOOP-9473.branch-1.patch, HADOOP-9473.patch,
HADOOP-9473.patch
typo:
{code}
Index: src/core/org/apache/hadoop/fs/FileUtil.java
===
--- src/core/org/apache/hadoop/fs/FileUtil.java (revision 1467295)
+++ src/core/org/apache/hadoop/fs/FileUtil.java (working copy)
@@ -178,7 +178,7 @@
// Check if dest is directory
if (!dstFS.exists(dst)) {
throw new IOException(` + dst +': specified destination directory
+
-doest not exist);
+does not exist);
} else {
FileStatus sdst = dstFS.getFileStatus(dst);
if (!sdst.isDir())
{code}
--
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-9473) typo in FileUtil copy() method
[
https://issues.apache.org/jira/browse/HADOOP-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HADOOP-9473:
--
Attachment: (was: HADOOP-9473.patch)
typo in FileUtil copy() method
--
Key: HADOOP-9473
URL: https://issues.apache.org/jira/browse/HADOOP-9473
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 2.0.0-alpha, 1.1.2
Reporter: Glen Mazza
Priority: Trivial
Fix For: 1.2.0, 2.0.5-beta
Attachments: HADOOP-9473.branch-1.patch, HADOOP-9473.patch
typo:
{code}
Index: src/core/org/apache/hadoop/fs/FileUtil.java
===
--- src/core/org/apache/hadoop/fs/FileUtil.java (revision 1467295)
+++ src/core/org/apache/hadoop/fs/FileUtil.java (working copy)
@@ -178,7 +178,7 @@
// Check if dest is directory
if (!dstFS.exists(dst)) {
throw new IOException(` + dst +': specified destination directory
+
-doest not exist);
+does not exist);
} else {
FileStatus sdst = dstFS.getFileStatus(dst);
if (!sdst.isDir())
{code}
--
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-9473) typo in FileUtil copy() method
[
https://issues.apache.org/jira/browse/HADOOP-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HADOOP-9473:
--
Attachment: HADOOP-9473-update-testConf-b1.2.patch
Rename the patch.
typo in FileUtil copy() method
--
Key: HADOOP-9473
URL: https://issues.apache.org/jira/browse/HADOOP-9473
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 2.0.0-alpha, 1.1.2
Reporter: Glen Mazza
Priority: Trivial
Fix For: 1.2.0, 2.0.5-beta
Attachments: HADOOP-9473.branch-1.patch, HADOOP-9473.patch,
HADOOP-9473-update-testConf-b1.2.patch
typo:
{code}
Index: src/core/org/apache/hadoop/fs/FileUtil.java
===
--- src/core/org/apache/hadoop/fs/FileUtil.java (revision 1467295)
+++ src/core/org/apache/hadoop/fs/FileUtil.java (working copy)
@@ -178,7 +178,7 @@
// Check if dest is directory
if (!dstFS.exists(dst)) {
throw new IOException(` + dst +': specified destination directory
+
-doest not exist);
+does not exist);
} else {
FileStatus sdst = dstFS.getFileStatus(dst);
if (!sdst.isDir())
{code}
--
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-9479) Ability to plugin custom authentication mechanism based on Jaas and Sasl
Benoy Antony created HADOOP-9479: Summary: Ability to plugin custom authentication mechanism based on Jaas and Sasl Key: HADOOP-9479 URL: https://issues.apache.org/jira/browse/HADOOP-9479 Project: Hadoop Common Issue Type: Sub-task Components: security Reporter: Benoy Antony Assignee: Benoy Antony Currently, it is not possible to hookup new/modified authentication mechanism to Hadoop. The task is to create an extension in hadoop to plugin new Authentication mechanism. The new authentication mechanism should have both Jaas and Sasl implementations. -- 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] [Work started] (HADOOP-9479) Ability to plugin custom authentication mechanism based on Jaas and Sasl
[ https://issues.apache.org/jira/browse/HADOOP-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-9479 started by Benoy Antony. Ability to plugin custom authentication mechanism based on Jaas and Sasl Key: HADOOP-9479 URL: https://issues.apache.org/jira/browse/HADOOP-9479 Project: Hadoop Common Issue Type: Sub-task Components: security Reporter: Benoy Antony Assignee: Benoy Antony Currently, it is not possible to hookup new/modified authentication mechanism to Hadoop. The task is to create an extension in hadoop to plugin new Authentication mechanism. The new authentication mechanism should have both Jaas and Sasl implementations. -- 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-9479) Ability to plugin custom authentication mechanism based on Jaas and Sasl
[ https://issues.apache.org/jira/browse/HADOOP-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HADOOP-9479: - Attachment: customauthentication.pdf HADOOP-9479.patch Attached is the first version of the patch to get guidance and feedback on the general approach. The document briefly explains the design and test. Ability to plugin custom authentication mechanism based on Jaas and Sasl Key: HADOOP-9479 URL: https://issues.apache.org/jira/browse/HADOOP-9479 Project: Hadoop Common Issue Type: Sub-task Components: security Reporter: Benoy Antony Assignee: Benoy Antony Attachments: customauthentication.pdf, HADOOP-9479.patch Currently, it is not possible to hookup new/modified authentication mechanism to Hadoop. The task is to create an extension in hadoop to plugin new Authentication mechanism. The new authentication mechanism should have both Jaas and Sasl implementations. -- 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-9296) Authenticating users from different realm without a trust relationship
[ https://issues.apache.org/jira/browse/HADOOP-9296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633485#comment-13633485 ] Benoy Antony commented on HADOOP-9296: -- To solve this problem, I am trying to add ability to plugin custom Authentication in Hadoop(HADOOP-9479). This allows us to keep our custom logic internally. Authenticating users from different realm without a trust relationship -- Key: HADOOP-9296 URL: https://issues.apache.org/jira/browse/HADOOP-9296 Project: Hadoop Common Issue Type: Improvement Components: security Reporter: Benoy Antony Assignee: Benoy Antony Attachments: HADOOP-9296-1.1.patch, multirealm.pdf Hadoop Masters (JobTracker and NameNode) and slaves (Data Node and TaskTracker) are part of the Hadoop domain, controlled by Hadoop Active Directory. The users belong to the CORP domain, controlled by the CORP Active Directory. In the absence of a one way trust from HADOOP DOMAIN to CORP DOMAIN, how will Hadoop Servers (JobTracker, NameNode) authenticate CORP users ? The solution and implementation details are in the attachement -- 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-9479) Ability to plugin custom authentication mechanisms based on Jaas and Sasl
[ https://issues.apache.org/jira/browse/HADOOP-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HADOOP-9479: - Summary: Ability to plugin custom authentication mechanisms based on Jaas and Sasl (was: Ability to plugin custom authentication mechanism based on Jaas and Sasl) Ability to plugin custom authentication mechanisms based on Jaas and Sasl - Key: HADOOP-9479 URL: https://issues.apache.org/jira/browse/HADOOP-9479 Project: Hadoop Common Issue Type: Sub-task Components: security Reporter: Benoy Antony Assignee: Benoy Antony Attachments: customauthentication.pdf, HADOOP-9479.patch Currently, it is not possible to hookup new/modified authentication mechanism to Hadoop. The task is to create an extension in hadoop to plugin new Authentication mechanism. The new authentication mechanism should have both Jaas and Sasl implementations. -- 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-9479) Ability to plugin custom authentication mechanisms based on Jaas and Sasl
[ https://issues.apache.org/jira/browse/HADOOP-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HADOOP-9479: - Attachment: (was: HADOOP-9479.patch) Ability to plugin custom authentication mechanisms based on Jaas and Sasl - Key: HADOOP-9479 URL: https://issues.apache.org/jira/browse/HADOOP-9479 Project: Hadoop Common Issue Type: Sub-task Components: security Reporter: Benoy Antony Assignee: Benoy Antony Attachments: customauthentication.pdf, HADOOP-9479.patch Currently, it is not possible to hookup new/modified authentication mechanism to Hadoop. The task is to create an extension in hadoop to plugin new Authentication mechanism. The new authentication mechanism should have both Jaas and Sasl implementations. -- 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-9479) Ability to plugin custom authentication mechanisms based on Jaas and Sasl
[ https://issues.apache.org/jira/browse/HADOOP-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HADOOP-9479: - Attachment: HADOOP-9479.patch Ability to plugin custom authentication mechanisms based on Jaas and Sasl - Key: HADOOP-9479 URL: https://issues.apache.org/jira/browse/HADOOP-9479 Project: Hadoop Common Issue Type: Sub-task Components: security Reporter: Benoy Antony Assignee: Benoy Antony Attachments: customauthentication.pdf, HADOOP-9479.patch Currently, it is not possible to hookup new/modified authentication mechanism to Hadoop. The task is to create an extension in hadoop to plugin new Authentication mechanism. The new authentication mechanism should have both Jaas and Sasl implementations. -- 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-9479) Ability to plugin custom authentication mechanisms based on Jaas and Sasl
[ https://issues.apache.org/jira/browse/HADOOP-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HADOOP-9479: - Attachment: (was: HADOOP-9479.patch) Ability to plugin custom authentication mechanisms based on Jaas and Sasl - Key: HADOOP-9479 URL: https://issues.apache.org/jira/browse/HADOOP-9479 Project: Hadoop Common Issue Type: Sub-task Components: security Reporter: Benoy Antony Assignee: Benoy Antony Attachments: customauthentication.pdf, HADOOP-9479.patch Currently, it is not possible to hookup new/modified authentication mechanism to Hadoop. The task is to create an extension in hadoop to plugin new Authentication mechanism. The new authentication mechanism should have both Jaas and Sasl implementations. -- 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-9479) Ability to plugin custom authentication mechanisms based on Jaas and Sasl
[ https://issues.apache.org/jira/browse/HADOOP-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HADOOP-9479: - Attachment: HADOOP-9479.patch Ability to plugin custom authentication mechanisms based on Jaas and Sasl - Key: HADOOP-9479 URL: https://issues.apache.org/jira/browse/HADOOP-9479 Project: Hadoop Common Issue Type: Sub-task Components: security Reporter: Benoy Antony Assignee: Benoy Antony Attachments: customauthentication.pdf, HADOOP-9479.patch Currently, it is not possible to hookup new/modified authentication mechanism to Hadoop. The task is to create an extension in hadoop to plugin new Authentication mechanism. The new authentication mechanism should have both Jaas and Sasl implementations. -- 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-9426) Hadoop should expose Jar location utilities on its public API
[ https://issues.apache.org/jira/browse/HADOOP-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633553#comment-13633553 ] Nick Dimiduk commented on HADOOP-9426: -- Bump. Hadoop should expose Jar location utilities on its public API - Key: HADOOP-9426 URL: https://issues.apache.org/jira/browse/HADOOP-9426 Project: Hadoop Common Issue Type: Bug Affects Versions: 1.0.0, 1.1.0, 2.0.0-alpha Reporter: Nick Dimiduk Attachments: 0001-HADOOP-9426-Promote-JarFinder-out-of-test-jar.patch, 0001-HADOOP-9426-Promote-JarFinder-out-of-test-jar.patch The facilities behind JobConf#setJarByClass and the JarFinder utility in test are both generally useful. As the core platform, these should be published as part of the public API. In addition to HBase, they are probably useful for Pig and Hive as well. See also HBASE-2588, HBASE-5317, HBASE-8140. -- 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-9426) Hadoop should expose Jar location utilities on its public API
[ https://issues.apache.org/jira/browse/HADOOP-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633561#comment-13633561 ] Alejandro Abdelnur commented on HADOOP-9426: bq. Are you suggesting that the parent process could locate the original jars in the distributed cache and use them? This is an acceptable solution from the HBase perspective. How might I resolve the paths? If you use the parent job conf to create your child job you'll get the distributed cached config for free. For example, in Oozie's case we populate the jobconf for child job in the oozie server and copy it to HDFS for the parent to loaded and add it to the child jobconf it is creating (actually oozie server cooks up the full job conf for the child job, the parent job just loads and uses it for the submission). Hadoop should expose Jar location utilities on its public API - Key: HADOOP-9426 URL: https://issues.apache.org/jira/browse/HADOOP-9426 Project: Hadoop Common Issue Type: Bug Affects Versions: 1.0.0, 1.1.0, 2.0.0-alpha Reporter: Nick Dimiduk Attachments: 0001-HADOOP-9426-Promote-JarFinder-out-of-test-jar.patch, 0001-HADOOP-9426-Promote-JarFinder-out-of-test-jar.patch The facilities behind JobConf#setJarByClass and the JarFinder utility in test are both generally useful. As the core platform, these should be published as part of the public API. In addition to HBase, they are probably useful for Pig and Hive as well. See also HBASE-2588, HBASE-5317, HBASE-8140. -- 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-9467) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name
[ https://issues.apache.org/jira/browse/HADOOP-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633604#comment-13633604 ] Suresh Srinivas commented on HADOOP-9467: - Luke, when committing please add both the contributors name. Can you please update the CHANGES.txt to include Chris's name? Metrics2 record filtering (.record.filter.include/exclude) does not filter by name -- Key: HADOOP-9467 URL: https://issues.apache.org/jira/browse/HADOOP-9467 Project: Hadoop Common Issue Type: Bug Components: metrics Affects Versions: 1.2.0, 3.0.0, 1-win, 2.0.4-alpha Reporter: Chris Nauroth Assignee: Chris Nauroth Fix For: 1.2.0, 2.0.4-alpha Attachments: HADOOP-9467.1.patch, HADOOP-9467-branch-1.1.patch Filtering by record considers only the record's tag for filtering and not the record's name. -- 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-9467) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name
[ https://issues.apache.org/jira/browse/HADOOP-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633688#comment-13633688 ] Luke Lu commented on HADOOP-9467: - Sure, will do. Looks like I misread Chris' credit line :) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name -- Key: HADOOP-9467 URL: https://issues.apache.org/jira/browse/HADOOP-9467 Project: Hadoop Common Issue Type: Bug Components: metrics Affects Versions: 1.2.0, 3.0.0, 1-win, 2.0.4-alpha Reporter: Chris Nauroth Assignee: Chris Nauroth Fix For: 1.2.0, 2.0.4-alpha Attachments: HADOOP-9467.1.patch, HADOOP-9467-branch-1.1.patch Filtering by record considers only the record's tag for filtering and not the record's name. -- 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-9467) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name
[ https://issues.apache.org/jira/browse/HADOOP-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633704#comment-13633704 ] Hudson commented on HADOOP-9467: Integrated in Hadoop-trunk-Commit #3619 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3619/]) Fix HADOOP-9467 attribution. (Revision 1468731) Result = SUCCESS llu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1468731 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt Metrics2 record filtering (.record.filter.include/exclude) does not filter by name -- Key: HADOOP-9467 URL: https://issues.apache.org/jira/browse/HADOOP-9467 Project: Hadoop Common Issue Type: Bug Components: metrics Affects Versions: 1.2.0, 3.0.0, 1-win, 2.0.4-alpha Reporter: Chris Nauroth Assignee: Chris Nauroth Fix For: 1.2.0, 2.0.4-alpha Attachments: HADOOP-9467.1.patch, HADOOP-9467-branch-1.1.patch Filtering by record considers only the record's tag for filtering and not the record's name. -- 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-9467) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name
[ https://issues.apache.org/jira/browse/HADOOP-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633715#comment-13633715 ] Chris Nauroth commented on HADOOP-9467: --- No worries, Luke. :-) Thanks for taking the time to correct it. Suresh, thank you for spotting this and requesting the correction. I hadn't noticed it myself. Metrics2 record filtering (.record.filter.include/exclude) does not filter by name -- Key: HADOOP-9467 URL: https://issues.apache.org/jira/browse/HADOOP-9467 Project: Hadoop Common Issue Type: Bug Components: metrics Affects Versions: 1.2.0, 3.0.0, 1-win, 2.0.4-alpha Reporter: Chris Nauroth Assignee: Chris Nauroth Fix For: 1.2.0, 2.0.4-alpha Attachments: HADOOP-9467.1.patch, HADOOP-9467-branch-1.1.patch Filtering by record considers only the record's tag for filtering and not the record's name. -- 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-9480) The windows installer should pick the config from src\packages\win\template\conf
Ivan Mitic created HADOOP-9480: -- Summary: The windows installer should pick the config from src\packages\win\template\conf Key: HADOOP-9480 URL: https://issues.apache.org/jira/browse/HADOOP-9480 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic We should pick the config files from the src\packages\win\template\conf location rather than the conf\ location in the Windows installer. Reported by [~mostafae]. -- 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-9480) The windows installer should pick the config from src\packages\win\template\conf
[ https://issues.apache.org/jira/browse/HADOOP-9480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Mitic updated HADOOP-9480: --- Attachment: HADOOP-9480.branch-1-win.patch Attaching the patch. The patch does the following: - copies over conf\log4j.configuration templete to src\packages\win\template\conf - fixes a bug where Windows log4j config is installed in the bin dir instead of the conf dir (causing it not to be loaded) The windows installer should pick the config from src\packages\win\template\conf Key: HADOOP-9480 URL: https://issues.apache.org/jira/browse/HADOOP-9480 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9480.branch-1-win.patch We should pick the config files from the src\packages\win\template\conf location rather than the conf\ location in the Windows installer. Reported by [~mostafae]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-9475) Distcp issue
[ https://issues.apache.org/jira/browse/HADOOP-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers resolved HADOOP-9475. Resolution: Invalid Resolving as invalid per Steve's comment. Distcp issue Key: HADOOP-9475 URL: https://issues.apache.org/jira/browse/HADOOP-9475 Project: Hadoop Common Issue Type: Bug Reporter: Sambit Sahoo 2013-04-13 05:11:43,327 INFO org.apache.hadoop.util.NativeCodeLoader: Loaded the native-hadoop library 2013-04-13 05:11:43,439 INFO org.apache.hadoop.metrics.jvm.JvmMetrics: Initializing JVM Metrics with processName=MAP, sessionId= 2013-04-13 05:11:43,750 INFO org.apache.hadoop.mapred.MapTask: numReduceTasks: 0 2013-04-13 05:11:43,981 INFO org.apache.hadoop.io.compress.zlib.ZlibFactory: Successfully loaded initialized native-zlib library 2013-04-13 05:31:08,282 INFO org.apache.hadoop.mapred.Task: Task:attempt_201302011155_224614_m_09_0 is done. And is in the process of commiting 2013-04-13 05:31:09,359 INFO org.apache.hadoop.mapred.Task: Task attempt_201302011155_224614_m_09_0 is allowed to commit now 2013-04-13 05:31:09,937 INFO org.apache.hadoop.mapred.FileOutputCommitter: Saved output of task 'attempt_201302011155_224614_m_09_0' to /tmp/_distcp_logs_spti36 2013-04-13 05:31:09,939 INFO org.apache.hadoop.mapred.Task: Task 'attempt_201302011155_224614_m_09_0' done. 2013-04-13 05:31:09,942 INFO org.apache.hadoop.mapred.TaskLogsTruncater: Initializing logs' truncater with mapRetainSize=-1 and reduceRetainSize=-1 I am facing some delay during disctcp from one cluster to another. Here i am copying snappy compressed data. -- 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
