[jira] [Commented] (HADOOP-9485) inconsistent defaults for hadoop.rpc.socket.factory.class.default

2013-05-06 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HADOOP-9485:
---

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12581627/HADOOP-9485.006.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 3 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.

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

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

This message is automatically generated.

> inconsistent defaults for hadoop.rpc.socket.factory.class.default
> -
>
> Key: HADOOP-9485
> URL: https://issues.apache.org/jira/browse/HADOOP-9485
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: net
>Affects Versions: 2.0.5-beta
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HADOOP-9485.001.patch, HADOOP-9485.002.patch, 
> HADOOP-9485.003.patch, HADOOP-9485.004.patch, HADOOP-9485.005.patch, 
> HADOOP-9485.006.patch
>
>
> In {{core-default.xml}}, {{hadoop.rpc.socket.factory.class.default}} defaults 
> to {{org.apache.hadoop.net.StandardSocketFactory}}.  However, in 
> {{CommonConfigurationKeysPublic.java}}, there is no default for this key.  
> This is inconsistent (defaults in the code versus defaults in the XML files 
> should match.)  It also leads to problems with {{RemoteBlockReader2}}, since 
> the default {{SocketFactory}} creates a {{Socket}} without an associated 
> channel.  {{RemoteBlockReader2}} cannot use such a {{Socket}}.
> This bug only really becomes apparent when you create a {{Configuration}} 
> using the {{Configuration(loadDefaults=true)}} constructor.  Thanks to AB 
> Srinivasan for his help in discovering this bug.

--
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-9485) inconsistent defaults for hadoop.rpc.socket.factory.class.default

2013-05-03 Thread Colin Patrick McCabe (JIRA)

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

Colin Patrick McCabe commented on HADOOP-9485:
--

This laest patch (which Jenkins hasn't run yet) should do exactly that.  Only 
by explicitly setting it to null or empty will you get the null behavior.

> inconsistent defaults for hadoop.rpc.socket.factory.class.default
> -
>
> Key: HADOOP-9485
> URL: https://issues.apache.org/jira/browse/HADOOP-9485
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: net
>Affects Versions: 2.0.5-beta
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HADOOP-9485.001.patch, HADOOP-9485.002.patch, 
> HADOOP-9485.003.patch, HADOOP-9485.004.patch, HADOOP-9485.005.patch, 
> HADOOP-9485.006.patch
>
>
> In {{core-default.xml}}, {{hadoop.rpc.socket.factory.class.default}} defaults 
> to {{org.apache.hadoop.net.StandardSocketFactory}}.  However, in 
> {{CommonConfigurationKeysPublic.java}}, there is no default for this key.  
> This is inconsistent (defaults in the code versus defaults in the XML files 
> should match.)  It also leads to problems with {{RemoteBlockReader2}}, since 
> the default {{SocketFactory}} creates a {{Socket}} without an associated 
> channel.  {{RemoteBlockReader2}} cannot use such a {{Socket}}.
> This bug only really becomes apparent when you create a {{Configuration}} 
> using the {{Configuration(loadDefaults=true)}} constructor.  Thanks to AB 
> Srinivasan for his help in discovering this bug.

--
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-9485) inconsistent defaults for hadoop.rpc.socket.factory.class.default

2013-05-03 Thread Todd Lipcon (JIRA)

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

Todd Lipcon commented on HADOOP-9485:
-

Yea, I _think_ we can differentiate between "explicitly set to null" and "not 
explicitly set". Either way, I think I'd rather break one or two folks who are 
setting to null to get that behavior than have a default against the legacy 
blockreader which we'd like to eventually remove.

> inconsistent defaults for hadoop.rpc.socket.factory.class.default
> -
>
> Key: HADOOP-9485
> URL: https://issues.apache.org/jira/browse/HADOOP-9485
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: net
>Affects Versions: 2.0.5-beta
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HADOOP-9485.001.patch, HADOOP-9485.002.patch, 
> HADOOP-9485.003.patch, HADOOP-9485.004.patch, HADOOP-9485.005.patch, 
> HADOOP-9485.006.patch
>
>
> In {{core-default.xml}}, {{hadoop.rpc.socket.factory.class.default}} defaults 
> to {{org.apache.hadoop.net.StandardSocketFactory}}.  However, in 
> {{CommonConfigurationKeysPublic.java}}, there is no default for this key.  
> This is inconsistent (defaults in the code versus defaults in the XML files 
> should match.)  It also leads to problems with {{RemoteBlockReader2}}, since 
> the default {{SocketFactory}} creates a {{Socket}} without an associated 
> channel.  {{RemoteBlockReader2}} cannot use such a {{Socket}}.
> This bug only really becomes apparent when you create a {{Configuration}} 
> using the {{Configuration(loadDefaults=true)}} constructor.  Thanks to AB 
> Srinivasan for his help in discovering this bug.

--
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-9485) inconsistent defaults for hadoop.rpc.socket.factory.class.default

2013-05-02 Thread Colin Patrick McCabe (JIRA)

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

Colin Patrick McCabe commented on HADOOP-9485:
--

I think the issue here is that running without XML defaults works in branch-1, 
and when upgrading to branch-2 or a distribution based on that, people view 
this kind of regression as a stumbling block.

bq. Why is it risky to change the default in the code to match the default from 
the XML file? 

Currently, you can set {{hadoop.rpc.socket.factory.class.default = null}} and 
we'll use {{SocketFactory.getDefault()}}.  If we change this behavior we may 
break users who are relying on it.  It certainly breaks {{TestSaslRPC}}.  It 
would be an incompatible change that would probably cause problems for users.

I suppose we could make the code default to the same thing as the XML file, but 
not change the meaning of setting the key to null.  That might work.

> inconsistent defaults for hadoop.rpc.socket.factory.class.default
> -
>
> Key: HADOOP-9485
> URL: https://issues.apache.org/jira/browse/HADOOP-9485
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: net
>Affects Versions: 2.0.5-beta
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HADOOP-9485.001.patch, HADOOP-9485.002.patch, 
> HADOOP-9485.003.patch, HADOOP-9485.004.patch, HADOOP-9485.005.patch
>
>
> In {{core-default.xml}}, {{hadoop.rpc.socket.factory.class.default}} defaults 
> to {{org.apache.hadoop.net.StandardSocketFactory}}.  However, in 
> {{CommonConfigurationKeysPublic.java}}, there is no default for this key.  
> This is inconsistent (defaults in the code versus defaults in the XML files 
> should match.)  It also leads to problems with {{RemoteBlockReader2}}, since 
> the default {{SocketFactory}} creates a {{Socket}} without an associated 
> channel.  {{RemoteBlockReader2}} cannot use such a {{Socket}}.
> This bug only really becomes apparent when you create a {{Configuration}} 
> using the {{Configuration(loadDefaults=true)}} constructor.  Thanks to AB 
> Srinivasan for his help in discovering this bug.

--
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-9485) inconsistent defaults for hadoop.rpc.socket.factory.class.default

2013-05-01 Thread Todd Lipcon (JIRA)

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

Todd Lipcon commented on HADOOP-9485:
-

I disagree with the approach of having differing defaults between the code and 
the hdfs-default.xml. Why is it risky to change the default in the code to 
match the default from the XML file? 99.9% of non-buggy users should be using 
hdfs-default.xml (which is shipped in our jars) or manually overriding. If 
someone is relying on the behavior with the XML file not present, I don't think 
we need to maintain that case.

> inconsistent defaults for hadoop.rpc.socket.factory.class.default
> -
>
> Key: HADOOP-9485
> URL: https://issues.apache.org/jira/browse/HADOOP-9485
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: net
>Affects Versions: 2.0.5-beta
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HADOOP-9485.001.patch, HADOOP-9485.002.patch, 
> HADOOP-9485.003.patch, HADOOP-9485.004.patch, HADOOP-9485.005.patch
>
>
> In {{core-default.xml}}, {{hadoop.rpc.socket.factory.class.default}} defaults 
> to {{org.apache.hadoop.net.StandardSocketFactory}}.  However, in 
> {{CommonConfigurationKeysPublic.java}}, there is no default for this key.  
> This is inconsistent (defaults in the code versus defaults in the XML files 
> should match.)  It also leads to problems with {{RemoteBlockReader2}}, since 
> the default {{SocketFactory}} creates a {{Socket}} without an associated 
> channel.  {{RemoteBlockReader2}} cannot use such a {{Socket}}.
> This bug only really becomes apparent when you create a {{Configuration}} 
> using the {{Configuration(loadDefaults=true)}} constructor.  Thanks to AB 
> Srinivasan for his help in discovering this bug.

--
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-9485) inconsistent defaults for hadoop.rpc.socket.factory.class.default

2013-04-30 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HADOOP-9485:
---

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

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

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

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

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

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

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

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

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-hdfs-project/hadoop-hdfs.

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

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

This message is automatically generated.

> inconsistent defaults for hadoop.rpc.socket.factory.class.default
> -
>
> Key: HADOOP-9485
> URL: https://issues.apache.org/jira/browse/HADOOP-9485
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: net
>Affects Versions: 2.0.5-beta
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HADOOP-9485.001.patch, HADOOP-9485.002.patch, 
> HADOOP-9485.003.patch, HADOOP-9485.004.patch, HADOOP-9485.005.patch
>
>
> In {{core-default.xml}}, {{hadoop.rpc.socket.factory.class.default}} defaults 
> to {{org.apache.hadoop.net.StandardSocketFactory}}.  However, in 
> {{CommonConfigurationKeysPublic.java}}, there is no default for this key.  
> This is inconsistent (defaults in the code versus defaults in the XML files 
> should match.)  It also leads to problems with {{RemoteBlockReader2}}, since 
> the default {{SocketFactory}} creates a {{Socket}} without an associated 
> channel.  {{RemoteBlockReader2}} cannot use such a {{Socket}}.
> This bug only really becomes apparent when you create a {{Configuration}} 
> using the {{Configuration(loadDefaults=true)}} constructor.  Thanks to AB 
> Srinivasan for his help in discovering this bug.

--
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-9485) inconsistent defaults for hadoop.rpc.socket.factory.class.default

2013-04-30 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HADOOP-9485:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12581232/HADOOP-9485.004.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-hdfs-project/hadoop-hdfs:

  org.apache.hadoop.hdfs.TestDistributedFileSystem

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

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

This message is automatically generated.

> inconsistent defaults for hadoop.rpc.socket.factory.class.default
> -
>
> Key: HADOOP-9485
> URL: https://issues.apache.org/jira/browse/HADOOP-9485
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: net
>Affects Versions: 2.0.5-beta
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HADOOP-9485.001.patch, HADOOP-9485.002.patch, 
> HADOOP-9485.003.patch, HADOOP-9485.004.patch
>
>
> In {{core-default.xml}}, {{hadoop.rpc.socket.factory.class.default}} defaults 
> to {{org.apache.hadoop.net.StandardSocketFactory}}.  However, in 
> {{CommonConfigurationKeysPublic.java}}, there is no default for this key.  
> This is inconsistent (defaults in the code versus defaults in the XML files 
> should match.)  It also leads to problems with {{RemoteBlockReader2}}, since 
> the default {{SocketFactory}} creates a {{Socket}} without an associated 
> channel.  {{RemoteBlockReader2}} cannot use such a {{Socket}}.
> This bug only really becomes apparent when you create a {{Configuration}} 
> using the {{Configuration(loadDefaults=true)}} constructor.  Thanks to AB 
> Srinivasan for his help in discovering this bug.

--
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-9485) inconsistent defaults for hadoop.rpc.socket.factory.class.default

2013-04-29 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HADOOP-9485:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12581051/HADOOP-9485.003.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 hadoop-hdfs-project/hadoop-hdfs:

  org.apache.hadoop.ipc.TestSaslRPC
  org.apache.hadoop.hdfs.TestDistributedFileSystem

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

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

This message is automatically generated.

> inconsistent defaults for hadoop.rpc.socket.factory.class.default
> -
>
> Key: HADOOP-9485
> URL: https://issues.apache.org/jira/browse/HADOOP-9485
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: net
>Affects Versions: 2.0.5-beta
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HADOOP-9485.001.patch, HADOOP-9485.002.patch, 
> HADOOP-9485.003.patch
>
>
> In {{core-default.xml}}, {{hadoop.rpc.socket.factory.class.default}} defaults 
> to {{org.apache.hadoop.net.StandardSocketFactory}}.  However, in 
> {{CommonConfigurationKeysPublic.java}}, there is no default for this key.  
> This is inconsistent (defaults in the code versus defaults in the XML files 
> should match.)  It also leads to problems with {{RemoteBlockReader2}}, since 
> the default {{SocketFactory}} creates a {{Socket}} without an associated 
> channel.  {{RemoteBlockReader2}} cannot use such a {{Socket}}.
> This bug only really becomes apparent when you create a {{Configuration}} 
> using the {{Configuration(loadDefaults=true)}} constructor.  Thanks to AB 
> Srinivasan for his help in discovering this bug.

--
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-9485) inconsistent defaults for hadoop.rpc.socket.factory.class.default

2013-04-18 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HADOOP-9485:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12579451/HADOOP-9485.002.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 hadoop-hdfs-project/hadoop-hdfs:

  org.apache.hadoop.ipc.TestSaslRPC
  org.apache.hadoop.hdfs.TestDistributedFileSystem

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

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

This message is automatically generated.

> inconsistent defaults for hadoop.rpc.socket.factory.class.default
> -
>
> Key: HADOOP-9485
> URL: https://issues.apache.org/jira/browse/HADOOP-9485
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: net
>Affects Versions: 2.0.5-beta
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HADOOP-9485.001.patch, HADOOP-9485.002.patch
>
>
> In {{core-default.xml}}, {{hadoop.rpc.socket.factory.class.default}} defaults 
> to {{org.apache.hadoop.net.StandardSocketFactory}}.  However, in 
> {{CommonConfigurationKeysPublic.java}}, there is no default for this key.  
> This is inconsistent (defaults in the code versus defaults in the XML files 
> should match.)  It also leads to problems with {{RemoteBlockReader2}}, since 
> the default {{SocketFactory}} creates a {{Socket}} without an associated 
> channel.  {{RemoteBlockReader2}} cannot use such a {{Socket}}.
> This bug only really becomes apparent when you create a {{Configuration}} 
> using the {{Configuration(loadDefaults=true)}} constructor.  Thanks to AB 
> Srinivasan for his help in discovering this bug.

--
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-9485) inconsistent defaults for hadoop.rpc.socket.factory.class.default

2013-04-18 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HADOOP-9485:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12579448/HADOOP-9485.001.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:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-common-project/hadoop-common:

  org.apache.hadoop.ipc.TestSaslRPC

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

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

This message is automatically generated.

> inconsistent defaults for hadoop.rpc.socket.factory.class.default
> -
>
> Key: HADOOP-9485
> URL: https://issues.apache.org/jira/browse/HADOOP-9485
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: net
>Affects Versions: 2.0.5-beta
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HADOOP-9485.001.patch, HADOOP-9485.002.patch
>
>
> In {{core-default.xml}}, {{hadoop.rpc.socket.factory.class.default}} defaults 
> to {{org.apache.hadoop.net.StandardSocketFactory}}.  However, in 
> {{CommonConfigurationKeysPublic.java}}, there is no default for this key.  
> This is inconsistent (defaults in the code versus defaults in the XML files 
> should match.)  It also leads to problems with {{RemoteBlockReader2}}, since 
> the default {{SocketFactory}} creates a {{Socket}} without an associated 
> channel.  {{RemoteBlockReader2}} cannot use such a {{Socket}}.
> This bug only really becomes apparent when you create a {{Configuration}} 
> using the {{Configuration(loadDefaults=true)}} constructor.  Thanks to AB 
> Srinivasan for his help in discovering this bug.

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