[jira] [Commented] (HADOOP-8865) log warn when loading deprecated properties

2012-09-29 Thread Jianbin Wei (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466423#comment-13466423
 ] 

Jianbin Wei commented on HADOOP-8865:
-

Harsh,

Do you have any idea why the org.apache.hadoop.ha.TestZKFailoverController 
fails due to timeout?  I saw that the unit test also failed in HADOOP-8386 but 
the patch is accepted.  Should the tests be disabled?

https://issues.apache.org/jira/browse/HADOOP-8386?focusedCommentId=13466016&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13466016

Thanks.

Jianbin

> log warn when loading deprecated properties
> ---
>
> Key: HADOOP-8865
> URL: https://issues.apache.org/jira/browse/HADOOP-8865
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: conf
>Affects Versions: 3.0.0
>Reporter: Jianbin Wei
> Fix For: 3.0.0
>
> Attachments: HADOOP-8865.patch, HADOOP-8865.patch, HADOOP-8865.patch
>
>
> We need to log warn when loading deprecated properties. 

--
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-8865) log warn when loading deprecated properties

2012-09-29 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466421#comment-13466421
 ] 

Hadoop QA commented on HADOOP-8865:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12547148/HADOOP-8865.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-common-project/hadoop-common:

  org.apache.hadoop.ha.TestZKFailoverController

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1548//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1548//console

This message is automatically generated.

> log warn when loading deprecated properties
> ---
>
> Key: HADOOP-8865
> URL: https://issues.apache.org/jira/browse/HADOOP-8865
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: conf
>Affects Versions: 3.0.0
>Reporter: Jianbin Wei
> Fix For: 3.0.0
>
> Attachments: HADOOP-8865.patch, HADOOP-8865.patch, HADOOP-8865.patch
>
>
> We need to log warn when loading deprecated properties. 

--
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-8426) API to get info for deprecated key

2012-09-29 Thread Jianbin Wei (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466418#comment-13466418
 ] 

Jianbin Wei commented on HADOOP-8426:
-

{quote}
Using this API the user can judge in runtime to use the old key or new key.
{quote}

In which case that a user wants to use deprecated key?

> API to get info for deprecated key
> --
>
> Key: HADOOP-8426
> URL: https://issues.apache.org/jira/browse/HADOOP-8426
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: conf
>Affects Versions: 0.23.1
>Reporter: Subroto Sanyal
>
> The current version of Hadoop deprecates many keys but, takes care of adding 
> the new keys to the configuration accordingly.
> For the end user only logs are there which indicates the key is deprecated 
> and the message also suggests the new key to be used.
> I was thinking; there should be an API/Utility which could probably provide 
> the new key information when called with old key.
> Using this API the user can judge in runtime to use the old key or new key.
> Currently the Configuration provides an API only to check whether a key is 
> deprecated or not but, doesn't provides a way to get the corresponding new 
> key.

--
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-8865) log warn when loading deprecated properties

2012-09-29 Thread Jianbin Wei (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jianbin Wei updated HADOOP-8865:


Status: Patch Available  (was: Open)

> log warn when loading deprecated properties
> ---
>
> Key: HADOOP-8865
> URL: https://issues.apache.org/jira/browse/HADOOP-8865
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: conf
>Affects Versions: 3.0.0
>Reporter: Jianbin Wei
> Fix For: 3.0.0
>
> Attachments: HADOOP-8865.patch, HADOOP-8865.patch, HADOOP-8865.patch
>
>
> We need to log warn when loading deprecated properties. 

--
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-8865) log warn when loading deprecated properties

2012-09-29 Thread Jianbin Wei (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jianbin Wei updated HADOOP-8865:


Attachment: HADOOP-8865.patch

> log warn when loading deprecated properties
> ---
>
> Key: HADOOP-8865
> URL: https://issues.apache.org/jira/browse/HADOOP-8865
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: conf
>Affects Versions: 3.0.0
>Reporter: Jianbin Wei
> Fix For: 3.0.0
>
> Attachments: HADOOP-8865.patch, HADOOP-8865.patch, HADOOP-8865.patch
>
>
> We need to log warn when loading deprecated properties. 

--
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-8865) log warn when loading deprecated properties

2012-09-29 Thread Jianbin Wei (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jianbin Wei updated HADOOP-8865:


Status: Open  (was: Patch Available)

> log warn when loading deprecated properties
> ---
>
> Key: HADOOP-8865
> URL: https://issues.apache.org/jira/browse/HADOOP-8865
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: conf
>Affects Versions: 3.0.0
>Reporter: Jianbin Wei
> Fix For: 3.0.0
>
> Attachments: HADOOP-8865.patch, HADOOP-8865.patch, HADOOP-8865.patch
>
>
> We need to log warn when loading deprecated properties. 

--
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-8839) test-patch's -1 on @author tag presence doesn't cause a -1 to the overall result

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466326#comment-13466326
 ] 

Hudson commented on HADOOP-8839:


Integrated in Hadoop-Hdfs-trunk-Commit #2854 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2854/])
HADOOP-8839. test-patch's -1 on @author tag presence doesn't cause a -1 to 
the overall result. Contributed by Harsh J. (harsh) (Revision 1391884)

 Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391884
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> test-patch's -1 on @author tag presence doesn't cause a -1 to the overall 
> result
> 
>
> Key: HADOOP-8839
> URL: https://issues.apache.org/jira/browse/HADOOP-8839
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: build
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HADOOP-8839.patch
>
>
> As observed on HADOOP-8838.

--
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-8839) test-patch's -1 on @author tag presence doesn't cause a -1 to the overall result

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466324#comment-13466324
 ] 

Hudson commented on HADOOP-8839:


Integrated in Hadoop-Common-trunk-Commit #2791 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2791/])
HADOOP-8839. test-patch's -1 on @author tag presence doesn't cause a -1 to 
the overall result. Contributed by Harsh J. (harsh) (Revision 1391884)

 Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391884
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> test-patch's -1 on @author tag presence doesn't cause a -1 to the overall 
> result
> 
>
> Key: HADOOP-8839
> URL: https://issues.apache.org/jira/browse/HADOOP-8839
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: build
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HADOOP-8839.patch
>
>
> As observed on HADOOP-8838.

--
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-8839) test-patch's -1 on @author tag presence doesn't cause a -1 to the overall result

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466325#comment-13466325
 ] 

Hudson commented on HADOOP-8839:


Integrated in Hadoop-Mapreduce-trunk-Commit #2813 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2813/])
HADOOP-8839. test-patch's -1 on @author tag presence doesn't cause a -1 to 
the overall result. Contributed by Harsh J. (harsh) (Revision 1391884)

 Result = FAILURE
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391884
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> test-patch's -1 on @author tag presence doesn't cause a -1 to the overall 
> result
> 
>
> Key: HADOOP-8839
> URL: https://issues.apache.org/jira/browse/HADOOP-8839
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: build
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HADOOP-8839.patch
>
>
> As observed on HADOOP-8838.

--
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-8839) test-patch's -1 on @author tag presence doesn't cause a -1 to the overall result

2012-09-29 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated HADOOP-8839:


   Resolution: Fixed
Fix Version/s: 3.0.0
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

Thanks Aaron, committed to trunk.

> test-patch's -1 on @author tag presence doesn't cause a -1 to the overall 
> result
> 
>
> Key: HADOOP-8839
> URL: https://issues.apache.org/jira/browse/HADOOP-8839
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: build
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HADOOP-8839.patch
>
>
> As observed on HADOOP-8838.

--
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-8866) SampleQuantiles#query is O(N^2) instead of O(N)

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466232#comment-13466232
 ] 

Hudson commented on HADOOP-8866:


Integrated in Hadoop-Mapreduce-trunk #1211 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1211/])
HADOOP-8866. SampleQuantiles#query is O(N^2) instead of O(N). Contributed 
by Andrew Wang. (Revision 1391711)

 Result = FAILURE
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391711
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/util/SampleQuantiles.java


> SampleQuantiles#query is O(N^2) instead of O(N)
> ---
>
> Key: HADOOP-8866
> URL: https://issues.apache.org/jira/browse/HADOOP-8866
> Project: Hadoop Common
>  Issue Type: Improvement
>Affects Versions: 2.0.2-alpha
>Reporter: Andrew Wang
>Assignee: Andrew Wang
>Priority: Minor
> Fix For: 2.0.3-alpha
>
> Attachments: hdfs-3976-1.patch
>
>
> SampleQuantiles#query() does O(N) calls LinkedList#get() in a loop, rather 
> than using an iterator. This makes query O(N^2), rather than O(N).

--
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-8864) Addendum to HADOOP-8840: Add a coloring case for +0 results too.

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466230#comment-13466230
 ] 

Hudson commented on HADOOP-8864:


Integrated in Hadoop-Mapreduce-trunk #1211 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1211/])
HADOOP-8864. Addendum to HADOOP-8840: Add a coloring case for +0 results 
too. Contributed by Harsh J. (harsh) (Revision 1391480)

 Result = FAILURE
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391480
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> Addendum to HADOOP-8840: Add a coloring case for +0 results too.
> 
>
> Key: HADOOP-8864
> URL: https://issues.apache.org/jira/browse/HADOOP-8864
> Project: Hadoop Common
>  Issue Type: Improvement
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HADOOP-8864.patch
>
>
> Noticed on MAPREDUCE-3223 that we failed to cover coloring the +0 case we 
> print sometimes for doc-only patches. These can be colored green too.

--
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-8386) hadoop script doesn't work if 'cd' prints to stdout (default behavior in Ubuntu)

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466227#comment-13466227
 ] 

Hudson commented on HADOOP-8386:


Integrated in Hadoop-Mapreduce-trunk #1211 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1211/])
HADOOP-8386. hadoop script doesn't work if 'cd' prints to stdout (default 
behavior in Ubuntu). Contributed by Christopher Berner and Andy Isaacson. 
(harsh) (Revision 1391780)

 Result = FAILURE
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391780
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs
* /hadoop/common/trunk/hadoop-mapreduce-project/bin/mapred
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/bin/yarn


> hadoop script doesn't work if 'cd' prints to stdout (default behavior in 
> Ubuntu)
> 
>
> Key: HADOOP-8386
> URL: https://issues.apache.org/jira/browse/HADOOP-8386
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 1.0.2
> Environment: Ubuntu
>Reporter: Christopher Berner
>Assignee: Christopher Berner
> Fix For: 1.2.0, 3.0.0
>
> Attachments: hadoop-8386-1.diff, hadoop-8386-1.diff, 
> hadoop-8386.diff, hadoop.diff
>
>
> if the 'hadoop' script is run as 'bin/hadoop' on a distro where the 'cd' 
> command prints to stdout, the script will fail due to this line: 'bin=`cd 
> "$bin"; pwd`'
> Workaround: execute from the bin/ directory as './hadoop'
> Fix: change that line to 'bin=`cd "$bin" > /dev/null; pwd`'

--
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-8840) Fix the test-patch colorizer to cover all sorts of +1 lines.

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466224#comment-13466224
 ] 

Hudson commented on HADOOP-8840:


Integrated in Hadoop-Mapreduce-trunk #1211 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1211/])
HADOOP-8864. Addendum to HADOOP-8840: Add a coloring case for +0 results 
too. Contributed by Harsh J. (harsh) (Revision 1391480)

 Result = FAILURE
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391480
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> Fix the test-patch colorizer to cover all sorts of +1 lines.
> 
>
> Key: HADOOP-8840
> URL: https://issues.apache.org/jira/browse/HADOOP-8840
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: build
>Reporter: Harsh J
>Assignee: Harsh J
> Fix For: 3.0.0
>
> Attachments: HADOOP-8840.patch
>
>
> As noticed by Jason on HADOOP-8838, I missed some of the entries needed to be 
> colorized.

--
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-8866) SampleQuantiles#query is O(N^2) instead of O(N)

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466215#comment-13466215
 ] 

Hudson commented on HADOOP-8866:


Integrated in Hadoop-Hdfs-trunk #1180 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1180/])
HADOOP-8866. SampleQuantiles#query is O(N^2) instead of O(N). Contributed 
by Andrew Wang. (Revision 1391711)

 Result = SUCCESS
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391711
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/util/SampleQuantiles.java


> SampleQuantiles#query is O(N^2) instead of O(N)
> ---
>
> Key: HADOOP-8866
> URL: https://issues.apache.org/jira/browse/HADOOP-8866
> Project: Hadoop Common
>  Issue Type: Improvement
>Affects Versions: 2.0.2-alpha
>Reporter: Andrew Wang
>Assignee: Andrew Wang
>Priority: Minor
> Fix For: 2.0.3-alpha
>
> Attachments: hdfs-3976-1.patch
>
>
> SampleQuantiles#query() does O(N) calls LinkedList#get() in a loop, rather 
> than using an iterator. This makes query O(N^2), rather than O(N).

--
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-8864) Addendum to HADOOP-8840: Add a coloring case for +0 results too.

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466213#comment-13466213
 ] 

Hudson commented on HADOOP-8864:


Integrated in Hadoop-Hdfs-trunk #1180 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1180/])
HADOOP-8864. Addendum to HADOOP-8840: Add a coloring case for +0 results 
too. Contributed by Harsh J. (harsh) (Revision 1391480)

 Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391480
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> Addendum to HADOOP-8840: Add a coloring case for +0 results too.
> 
>
> Key: HADOOP-8864
> URL: https://issues.apache.org/jira/browse/HADOOP-8864
> Project: Hadoop Common
>  Issue Type: Improvement
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HADOOP-8864.patch
>
>
> Noticed on MAPREDUCE-3223 that we failed to cover coloring the +0 case we 
> print sometimes for doc-only patches. These can be colored green too.

--
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-8840) Fix the test-patch colorizer to cover all sorts of +1 lines.

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466207#comment-13466207
 ] 

Hudson commented on HADOOP-8840:


Integrated in Hadoop-Hdfs-trunk #1180 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1180/])
HADOOP-8864. Addendum to HADOOP-8840: Add a coloring case for +0 results 
too. Contributed by Harsh J. (harsh) (Revision 1391480)

 Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391480
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> Fix the test-patch colorizer to cover all sorts of +1 lines.
> 
>
> Key: HADOOP-8840
> URL: https://issues.apache.org/jira/browse/HADOOP-8840
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: build
>Reporter: Harsh J
>Assignee: Harsh J
> Fix For: 3.0.0
>
> Attachments: HADOOP-8840.patch
>
>
> As noticed by Jason on HADOOP-8838, I missed some of the entries needed to be 
> colorized.

--
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-8386) hadoop script doesn't work if 'cd' prints to stdout (default behavior in Ubuntu)

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466210#comment-13466210
 ] 

Hudson commented on HADOOP-8386:


Integrated in Hadoop-Hdfs-trunk #1180 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1180/])
HADOOP-8386. hadoop script doesn't work if 'cd' prints to stdout (default 
behavior in Ubuntu). Contributed by Christopher Berner and Andy Isaacson. 
(harsh) (Revision 1391780)

 Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391780
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs
* /hadoop/common/trunk/hadoop-mapreduce-project/bin/mapred
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/bin/yarn


> hadoop script doesn't work if 'cd' prints to stdout (default behavior in 
> Ubuntu)
> 
>
> Key: HADOOP-8386
> URL: https://issues.apache.org/jira/browse/HADOOP-8386
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 1.0.2
> Environment: Ubuntu
>Reporter: Christopher Berner
>Assignee: Christopher Berner
> Fix For: 1.2.0, 3.0.0
>
> Attachments: hadoop-8386-1.diff, hadoop-8386-1.diff, 
> hadoop-8386.diff, hadoop.diff
>
>
> if the 'hadoop' script is run as 'bin/hadoop' on a distro where the 'cd' 
> command prints to stdout, the script will fail due to this line: 'bin=`cd 
> "$bin"; pwd`'
> Workaround: execute from the bin/ directory as './hadoop'
> Fix: change that line to 'bin=`cd "$bin" > /dev/null; pwd`'

--
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-8386) hadoop script doesn't work if 'cd' prints to stdout (default behavior in Ubuntu)

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466180#comment-13466180
 ] 

Hudson commented on HADOOP-8386:


Integrated in Hadoop-Mapreduce-trunk-Commit #2811 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2811/])
HADOOP-8386. hadoop script doesn't work if 'cd' prints to stdout (default 
behavior in Ubuntu). Contributed by Christopher Berner and Andy Isaacson. 
(harsh) (Revision 1391780)

 Result = FAILURE
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391780
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs
* /hadoop/common/trunk/hadoop-mapreduce-project/bin/mapred
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/bin/yarn


> hadoop script doesn't work if 'cd' prints to stdout (default behavior in 
> Ubuntu)
> 
>
> Key: HADOOP-8386
> URL: https://issues.apache.org/jira/browse/HADOOP-8386
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 1.0.2
> Environment: Ubuntu
>Reporter: Christopher Berner
>Assignee: Christopher Berner
> Fix For: 1.2.0, 3.0.0
>
> Attachments: hadoop-8386-1.diff, hadoop-8386-1.diff, 
> hadoop-8386.diff, hadoop.diff
>
>
> if the 'hadoop' script is run as 'bin/hadoop' on a distro where the 'cd' 
> command prints to stdout, the script will fail due to this line: 'bin=`cd 
> "$bin"; pwd`'
> Workaround: execute from the bin/ directory as './hadoop'
> Fix: change that line to 'bin=`cd "$bin" > /dev/null; pwd`'

--
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-8386) hadoop script doesn't work if 'cd' prints to stdout (default behavior in Ubuntu)

2012-09-29 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated HADOOP-8386:


Target Version/s:   (was: 1.2.0, 3.0.0)

> hadoop script doesn't work if 'cd' prints to stdout (default behavior in 
> Ubuntu)
> 
>
> Key: HADOOP-8386
> URL: https://issues.apache.org/jira/browse/HADOOP-8386
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 1.0.2
> Environment: Ubuntu
>Reporter: Christopher Berner
>Assignee: Christopher Berner
> Fix For: 1.2.0, 3.0.0
>
> Attachments: hadoop-8386-1.diff, hadoop-8386-1.diff, 
> hadoop-8386.diff, hadoop.diff
>
>
> if the 'hadoop' script is run as 'bin/hadoop' on a distro where the 'cd' 
> command prints to stdout, the script will fail due to this line: 'bin=`cd 
> "$bin"; pwd`'
> Workaround: execute from the bin/ directory as './hadoop'
> Fix: change that line to 'bin=`cd "$bin" > /dev/null; pwd`'

--
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-8386) hadoop script doesn't work if 'cd' prints to stdout (default behavior in Ubuntu)

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466179#comment-13466179
 ] 

Hudson commented on HADOOP-8386:


Integrated in Hadoop-Common-trunk-Commit #2789 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2789/])
HADOOP-8386. hadoop script doesn't work if 'cd' prints to stdout (default 
behavior in Ubuntu). Contributed by Christopher Berner and Andy Isaacson. 
(harsh) (Revision 1391780)

 Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391780
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs
* /hadoop/common/trunk/hadoop-mapreduce-project/bin/mapred
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/bin/yarn


> hadoop script doesn't work if 'cd' prints to stdout (default behavior in 
> Ubuntu)
> 
>
> Key: HADOOP-8386
> URL: https://issues.apache.org/jira/browse/HADOOP-8386
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 1.0.2
> Environment: Ubuntu
>Reporter: Christopher Berner
>Assignee: Christopher Berner
> Fix For: 1.2.0, 3.0.0
>
> Attachments: hadoop-8386-1.diff, hadoop-8386-1.diff, 
> hadoop-8386.diff, hadoop.diff
>
>
> if the 'hadoop' script is run as 'bin/hadoop' on a distro where the 'cd' 
> command prints to stdout, the script will fail due to this line: 'bin=`cd 
> "$bin"; pwd`'
> Workaround: execute from the bin/ directory as './hadoop'
> Fix: change that line to 'bin=`cd "$bin" > /dev/null; pwd`'

--
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-8386) hadoop script doesn't work if 'cd' prints to stdout (default behavior in Ubuntu)

2012-09-29 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated HADOOP-8386:


   Resolution: Fixed
Fix Version/s: 3.0.0
   1.2.0
   Status: Resolved  (was: Patch Available)

I've committed the fix for both trunk and branch-1 scripts.

Thanks Christopher and Andy!

> hadoop script doesn't work if 'cd' prints to stdout (default behavior in 
> Ubuntu)
> 
>
> Key: HADOOP-8386
> URL: https://issues.apache.org/jira/browse/HADOOP-8386
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 1.0.2
> Environment: Ubuntu
>Reporter: Christopher Berner
>Assignee: Christopher Berner
> Fix For: 1.2.0, 3.0.0
>
> Attachments: hadoop-8386-1.diff, hadoop-8386-1.diff, 
> hadoop-8386.diff, hadoop.diff
>
>
> if the 'hadoop' script is run as 'bin/hadoop' on a distro where the 'cd' 
> command prints to stdout, the script will fail due to this line: 'bin=`cd 
> "$bin"; pwd`'
> Workaround: execute from the bin/ directory as './hadoop'
> Fix: change that line to 'bin=`cd "$bin" > /dev/null; pwd`'

--
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-8386) hadoop script doesn't work if 'cd' prints to stdout (default behavior in Ubuntu)

2012-09-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466177#comment-13466177
 ] 

Hudson commented on HADOOP-8386:


Integrated in Hadoop-Hdfs-trunk-Commit #2852 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2852/])
HADOOP-8386. hadoop script doesn't work if 'cd' prints to stdout (default 
behavior in Ubuntu). Contributed by Christopher Berner and Andy Isaacson. 
(harsh) (Revision 1391780)

 Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391780
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs
* /hadoop/common/trunk/hadoop-mapreduce-project/bin/mapred
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/bin/yarn


> hadoop script doesn't work if 'cd' prints to stdout (default behavior in 
> Ubuntu)
> 
>
> Key: HADOOP-8386
> URL: https://issues.apache.org/jira/browse/HADOOP-8386
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 1.0.2
> Environment: Ubuntu
>Reporter: Christopher Berner
>Assignee: Christopher Berner
> Attachments: hadoop-8386-1.diff, hadoop-8386-1.diff, 
> hadoop-8386.diff, hadoop.diff
>
>
> if the 'hadoop' script is run as 'bin/hadoop' on a distro where the 'cd' 
> command prints to stdout, the script will fail due to this line: 'bin=`cd 
> "$bin"; pwd`'
> Workaround: execute from the bin/ directory as './hadoop'
> Fix: change that line to 'bin=`cd "$bin" > /dev/null; pwd`'

--
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-8386) hadoop script doesn't work if 'cd' prints to stdout (default behavior in Ubuntu)

2012-09-29 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated HADOOP-8386:


Assignee: Christopher Berner

> hadoop script doesn't work if 'cd' prints to stdout (default behavior in 
> Ubuntu)
> 
>
> Key: HADOOP-8386
> URL: https://issues.apache.org/jira/browse/HADOOP-8386
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 1.0.2
> Environment: Ubuntu
>Reporter: Christopher Berner
>Assignee: Christopher Berner
> Attachments: hadoop-8386-1.diff, hadoop-8386-1.diff, 
> hadoop-8386.diff, hadoop.diff
>
>
> if the 'hadoop' script is run as 'bin/hadoop' on a distro where the 'cd' 
> command prints to stdout, the script will fail due to this line: 'bin=`cd 
> "$bin"; pwd`'
> Workaround: execute from the bin/ directory as './hadoop'
> Fix: change that line to 'bin=`cd "$bin" > /dev/null; pwd`'

--
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-8386) hadoop script doesn't work if 'cd' prints to stdout (default behavior in Ubuntu)

2012-09-29 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated HADOOP-8386:


Attachment: hadoop-8386-1.diff

Thanks Chris and Andy. Fixed mapred, yarn, and hdfs scripts as well (for trunk).

> hadoop script doesn't work if 'cd' prints to stdout (default behavior in 
> Ubuntu)
> 
>
> Key: HADOOP-8386
> URL: https://issues.apache.org/jira/browse/HADOOP-8386
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 1.0.2
> Environment: Ubuntu
>Reporter: Christopher Berner
> Attachments: hadoop-8386-1.diff, hadoop-8386-1.diff, 
> hadoop-8386.diff, hadoop.diff
>
>
> if the 'hadoop' script is run as 'bin/hadoop' on a distro where the 'cd' 
> command prints to stdout, the script will fail due to this line: 'bin=`cd 
> "$bin"; pwd`'
> Workaround: execute from the bin/ directory as './hadoop'
> Fix: change that line to 'bin=`cd "$bin" > /dev/null; pwd`'

--
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-8386) hadoop script doesn't work if 'cd' prints to stdout (default behavior in Ubuntu)

2012-09-29 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated HADOOP-8386:


Target Version/s: 1.2.0, 3.0.0
Hadoop Flags: Reviewed

> hadoop script doesn't work if 'cd' prints to stdout (default behavior in 
> Ubuntu)
> 
>
> Key: HADOOP-8386
> URL: https://issues.apache.org/jira/browse/HADOOP-8386
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 1.0.2
> Environment: Ubuntu
>Reporter: Christopher Berner
> Attachments: hadoop-8386-1.diff, hadoop-8386-1.diff, 
> hadoop-8386.diff, hadoop.diff
>
>
> if the 'hadoop' script is run as 'bin/hadoop' on a distro where the 'cd' 
> command prints to stdout, the script will fail due to this line: 'bin=`cd 
> "$bin"; pwd`'
> Workaround: execute from the bin/ directory as './hadoop'
> Fix: change that line to 'bin=`cd "$bin" > /dev/null; pwd`'

--
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-8589) ViewFs tests fail when tests and home dirs are nested

2012-09-29 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated HADOOP-8589:


Target Version/s: 3.0.0, 0.23.4, 2.0.3-alpha  (was: 0.23.2)

> ViewFs tests fail when tests and home dirs are nested
> -
>
> Key: HADOOP-8589
> URL: https://issues.apache.org/jira/browse/HADOOP-8589
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: fs, test
>Affects Versions: 0.23.1, 2.0.0-alpha
>Reporter: Andrey Klochkov
>Assignee: Andrey Klochkov
> Attachments: HADOOP-8589.patch, HADOOP-8589.patch, HADOOP-8859.patch
>
>
> TestFSMainOperationsLocalFileSystem fails in case when the test root 
> directory is under the user's home directory, and the user's home dir is 
> deeper than 2 levels from /. This happens with the default 1-node 
> installation of Jenkins. 
> This is the failure log:
> {code}
> org.apache.hadoop.fs.FileAlreadyExistsException: Path /var already exists as 
> dir; cannot create link here
>   at org.apache.hadoop.fs.viewfs.InodeTree.createLink(InodeTree.java:244)
>   at org.apache.hadoop.fs.viewfs.InodeTree.(InodeTree.java:334)
>   at 
> org.apache.hadoop.fs.viewfs.ViewFileSystem$1.(ViewFileSystem.java:167)
>   at 
> org.apache.hadoop.fs.viewfs.ViewFileSystem.initialize(ViewFileSystem.java:167)
>   at 
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2094)
>   at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:79)
>   at 
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2128)
>   at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2110)
>   at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:290)
>   at 
> org.apache.hadoop.fs.viewfs.ViewFileSystemTestSetup.setupForViewFileSystem(ViewFileSystemTestSetup.java:76)
>   at 
> org.apache.hadoop.fs.viewfs.TestFSMainOperationsLocalFileSystem.setUp(TestFSMainOperationsLocalFileSystem.java:40)
> ...
> Standard Output
> 2012-07-11 22:07:20,239 INFO  mortbay.log (Slf4jLog.java:info(67)) - Home dir 
> base /var/lib
> {code}
> The reason for the failure is that the code tries to mount links for both 
> "/var" and "/var/lib", and it fails for the 2nd one as the "/var" is mounted 
> already.
> The fix was provided in HADOOP-8036 but later it was reverted in HADOOP-8129.

--
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-8589) ViewFs tests fail when tests and home dirs are nested

2012-09-29 Thread Harsh J (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466168#comment-13466168
 ] 

Harsh J commented on HADOOP-8589:
-

Daryn - Want to give this another look? Looks clean and passes on /foo, 
/home/harsh and /home/foo/bar as home directories.

> ViewFs tests fail when tests and home dirs are nested
> -
>
> Key: HADOOP-8589
> URL: https://issues.apache.org/jira/browse/HADOOP-8589
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: fs, test
>Affects Versions: 0.23.1, 2.0.0-alpha
>Reporter: Andrey Klochkov
>Assignee: Andrey Klochkov
> Attachments: HADOOP-8589.patch, HADOOP-8589.patch, HADOOP-8859.patch
>
>
> TestFSMainOperationsLocalFileSystem fails in case when the test root 
> directory is under the user's home directory, and the user's home dir is 
> deeper than 2 levels from /. This happens with the default 1-node 
> installation of Jenkins. 
> This is the failure log:
> {code}
> org.apache.hadoop.fs.FileAlreadyExistsException: Path /var already exists as 
> dir; cannot create link here
>   at org.apache.hadoop.fs.viewfs.InodeTree.createLink(InodeTree.java:244)
>   at org.apache.hadoop.fs.viewfs.InodeTree.(InodeTree.java:334)
>   at 
> org.apache.hadoop.fs.viewfs.ViewFileSystem$1.(ViewFileSystem.java:167)
>   at 
> org.apache.hadoop.fs.viewfs.ViewFileSystem.initialize(ViewFileSystem.java:167)
>   at 
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2094)
>   at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:79)
>   at 
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2128)
>   at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2110)
>   at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:290)
>   at 
> org.apache.hadoop.fs.viewfs.ViewFileSystemTestSetup.setupForViewFileSystem(ViewFileSystemTestSetup.java:76)
>   at 
> org.apache.hadoop.fs.viewfs.TestFSMainOperationsLocalFileSystem.setUp(TestFSMainOperationsLocalFileSystem.java:40)
> ...
> Standard Output
> 2012-07-11 22:07:20,239 INFO  mortbay.log (Slf4jLog.java:info(67)) - Home dir 
> base /var/lib
> {code}
> The reason for the failure is that the code tries to mount links for both 
> "/var" and "/var/lib", and it fails for the 2nd one as the "/var" is mounted 
> already.
> The fix was provided in HADOOP-8036 but later it was reverted in HADOOP-8129.

--
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-8865) log warn when loading deprecated properties

2012-09-29 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466153#comment-13466153
 ] 

Hadoop QA commented on HADOOP-8865:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12547099/HADOOP-8865.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-common-project/hadoop-common:

  org.apache.hadoop.ha.TestZKFailoverController

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1546//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1546//console

This message is automatically generated.

> log warn when loading deprecated properties
> ---
>
> Key: HADOOP-8865
> URL: https://issues.apache.org/jira/browse/HADOOP-8865
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: conf
>Affects Versions: 3.0.0
>Reporter: Jianbin Wei
> Fix For: 3.0.0
>
> Attachments: HADOOP-8865.patch, HADOOP-8865.patch
>
>
> We need to log warn when loading deprecated properties. 

--
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-8851) Use -XX:+HeapDumpOnOutOfMemoryError JVM option in the forked tests

2012-09-29 Thread Aaron T. Myers (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466152#comment-13466152
 ] 

Aaron T. Myers commented on HADOOP-8851:


Hi Ivan, can you comment on what testing you've done of this patch? Did you 
perhaps modify a test to artificially induce an OOME and then observe that the 
heap dump showed up in the test output? For that matter, where does the heap 
dump show up? On the console? In some test output file?

> Use -XX:+HeapDumpOnOutOfMemoryError JVM option in the forked tests
> --
>
> Key: HADOOP-8851
> URL: https://issues.apache.org/jira/browse/HADOOP-8851
> Project: Hadoop Common
>  Issue Type: Improvement
>Reporter: Ivan A. Veselovsky
>Assignee: Ivan A. Veselovsky
>Priority: Minor
> Attachments: HADOOP-8851-vs-trunk.patch
>
>
> This can help to reveal the cause of issue in the event of OOME in tests.
> Suggested patch attached.

--
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-8851) Use -XX:+HeapDumpOnOutOfMemoryError JVM option in the forked tests

2012-09-29 Thread Aaron T. Myers (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aaron T. Myers reassigned HADOOP-8851:
--

Assignee: Ivan A. Veselovsky

> Use -XX:+HeapDumpOnOutOfMemoryError JVM option in the forked tests
> --
>
> Key: HADOOP-8851
> URL: https://issues.apache.org/jira/browse/HADOOP-8851
> Project: Hadoop Common
>  Issue Type: Improvement
>Reporter: Ivan A. Veselovsky
>Assignee: Ivan A. Veselovsky
>Priority: Minor
> Attachments: HADOOP-8851-vs-trunk.patch
>
>
> This can help to reveal the cause of issue in the event of OOME in tests.
> Suggested patch attached.

--
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-8865) log warn when loading deprecated properties

2012-09-29 Thread Jianbin Wei (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jianbin Wei updated HADOOP-8865:


Status: Patch Available  (was: Open)

> log warn when loading deprecated properties
> ---
>
> Key: HADOOP-8865
> URL: https://issues.apache.org/jira/browse/HADOOP-8865
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: conf
>Affects Versions: 3.0.0
>Reporter: Jianbin Wei
> Fix For: 3.0.0
>
> Attachments: HADOOP-8865.patch, HADOOP-8865.patch
>
>
> We need to log warn when loading deprecated properties. 

--
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-8865) log warn when loading deprecated properties

2012-09-29 Thread Jianbin Wei (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jianbin Wei updated HADOOP-8865:


Status: Open  (was: Patch Available)

> log warn when loading deprecated properties
> ---
>
> Key: HADOOP-8865
> URL: https://issues.apache.org/jira/browse/HADOOP-8865
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: conf
>Affects Versions: 3.0.0
>Reporter: Jianbin Wei
> Fix For: 3.0.0
>
> Attachments: HADOOP-8865.patch, HADOOP-8865.patch
>
>
> We need to log warn when loading deprecated properties. 

--
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-8865) log warn when loading deprecated properties

2012-09-29 Thread Jianbin Wei (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jianbin Wei updated HADOOP-8865:


Attachment: HADOOP-8865.patch

> log warn when loading deprecated properties
> ---
>
> Key: HADOOP-8865
> URL: https://issues.apache.org/jira/browse/HADOOP-8865
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: conf
>Affects Versions: 3.0.0
>Reporter: Jianbin Wei
> Fix For: 3.0.0
>
> Attachments: HADOOP-8865.patch, HADOOP-8865.patch
>
>
> We need to log warn when loading deprecated properties. 

--
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