[jira] [Commented] (HADOOP-11535) TableMapping related tests failed due to 'correct' resolving for test hostname
[
https://issues.apache.org/jira/browse/HADOOP-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14308826#comment-14308826
]
Hadoop QA commented on HADOOP-11535:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696981/HADOOP-11535-v1.patch
against trunk revision 9d91069.
{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}. There were no new javadoc 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 2.0.3) 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.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5614//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5614//console
This message is automatically generated.
TableMapping related tests failed due to 'correct' resolving for test hostname
--
Key: HADOOP-11535
URL: https://issues.apache.org/jira/browse/HADOOP-11535
Project: Hadoop Common
Issue Type: Test
Reporter: Kai Zheng
Assignee: Kai Zheng
Priority: Minor
Attachments: HADOOP-11535-v1.patch
When mvn test in my environment, it reported the following.
{noformat}
Failed tests:
TestTableMapping.testClearingCachedMappings:144 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testTableCaching:79 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testResolve:56 expected:/[rack1] but
was:/[default-rack]
{noformat}
It's caused by the good resolving for the 'bad test' hostname 'a.b.c' as
follows.
{noformat}
[drankye@zkdesk hadoop-common-project]$ ping a.b.c
PING a.b.c (220.250.64.228) 56(84) bytes of data.
{noformat}
I understand it may happen in just my local environment, and document this
just in case others also meet this. We may use even worse hostname than
'a.b.c' to avoid such situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11535) TableMapping related tests failed due to 'correct' resolving for test hostname
[
https://issues.apache.org/jira/browse/HADOOP-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309078#comment-14309078
]
Steve Loughran commented on HADOOP-11535:
-
+1 for moving to ip addresses. anything that relies on DNS working is brittle
and prone to failure when you run the tests offline
TableMapping related tests failed due to 'correct' resolving for test hostname
--
Key: HADOOP-11535
URL: https://issues.apache.org/jira/browse/HADOOP-11535
Project: Hadoop Common
Issue Type: Test
Reporter: Kai Zheng
Assignee: Kai Zheng
Priority: Minor
Attachments: HADOOP-11535-v1.patch
When mvn test in my environment, it reported the following.
{noformat}
Failed tests:
TestTableMapping.testClearingCachedMappings:144 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testTableCaching:79 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testResolve:56 expected:/[rack1] but
was:/[default-rack]
{noformat}
It's caused by the good resolving for the 'bad test' hostname 'a.b.c' as
follows.
{noformat}
[drankye@zkdesk hadoop-common-project]$ ping a.b.c
PING a.b.c (220.250.64.228) 56(84) bytes of data.
{noformat}
I understand it may happen in just my local environment, and document this
just in case others also meet this. We may use even worse hostname than
'a.b.c' to avoid such situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11535) TableMapping related tests failed due to 'correct' resolving for test hostname
[
https://issues.apache.org/jira/browse/HADOOP-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14308682#comment-14308682
]
Kai Zheng commented on HADOOP-11535:
Hmmm, looks like it's not the case. Actually whatever bad or invalid hostname
is used, it can resolve to the fixed IP address in my network, as follows.
{noformat}
nslookup abc.invalid.test
Server: 10.248.2.5
Address:10.248.2.5#53
Non-authoritative answer:
Name: abc.invalid.test
Address: 220.250.64.228
{noformat}
So I thought in the tests we should not use hostname, instead use IP address,
to avoid such bad situation at all. I'm not sure if it's the typical or not,
but Java as nslookup does return non-authoritative answer when resolving a
domain name. Using domain name isn't necessary for the tests.
[~ste...@apache.org], do you agree we can change the test, not using domain
name like 'a.b.c', instead using IP address like '1.2.3.4' ? Thanks.
TableMapping related tests failed due to 'correct' resolving for test hostname
--
Key: HADOOP-11535
URL: https://issues.apache.org/jira/browse/HADOOP-11535
Project: Hadoop Common
Issue Type: Test
Reporter: Kai Zheng
Assignee: Kai Zheng
Priority: Minor
When mvn test in my environment, it reported the following.
{noformat}
Failed tests:
TestTableMapping.testClearingCachedMappings:144 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testTableCaching:79 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testResolve:56 expected:/[rack1] but
was:/[default-rack]
{noformat}
It's caused by the good resolving for the 'bad test' hostname 'a.b.c' as
follows.
{noformat}
[drankye@zkdesk hadoop-common-project]$ ping a.b.c
PING a.b.c (220.250.64.228) 56(84) bytes of data.
{noformat}
I understand it may happen in just my local environment, and document this
just in case others also meet this. We may use even worse hostname than
'a.b.c' to avoid such situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11535) TableMapping related tests failed due to 'correct' resolving for test hostname
[
https://issues.apache.org/jira/browse/HADOOP-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14308495#comment-14308495
]
Kai Zheng commented on HADOOP-11535:
Thanks Steve for the pointing. I checked it out and see the following domain
names are reserved.
{noformat}
.test
.example
.invalid
.localhost
example.com
example.net
example.org
{noformat}
So according to this, we should check the tests and replace the domain names
with the reserved ones, to make sure they won't resolve. Will provide a patch
accordingly.
TableMapping related tests failed due to 'correct' resolving for test hostname
--
Key: HADOOP-11535
URL: https://issues.apache.org/jira/browse/HADOOP-11535
Project: Hadoop Common
Issue Type: Test
Reporter: Kai Zheng
Assignee: Kai Zheng
Priority: Minor
When mvn test in my environment, it reported the following.
{noformat}
Failed tests:
TestTableMapping.testClearingCachedMappings:144 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testTableCaching:79 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testResolve:56 expected:/[rack1] but
was:/[default-rack]
{noformat}
It's caused by the good resolving for the 'bad test' hostname 'a.b.c' as
follows.
{noformat}
[drankye@zkdesk hadoop-common-project]$ ping a.b.c
PING a.b.c (220.250.64.228) 56(84) bytes of data.
{noformat}
I understand it may happen in just my local environment, and document this
just in case others also meet this. We may use even worse hostname than
'a.b.c' to avoid such situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11535) TableMapping related tests failed due to 'correct' resolving for test hostname
[
https://issues.apache.org/jira/browse/HADOOP-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303163#comment-14303163
]
Kai Zheng commented on HADOOP-11535:
Hi Steve, thanks for your response.
bq. the IETF mandates that these hostnames must never resolve
Would you clarify which hostnames not to resolve ? Does a.b.c be such one ?
Which IETF spec states this ?
I'd like to investigate a bit further, because it always resolves in my company
dev environment, which fails the tests.
Thanks.
TableMapping related tests failed due to 'correct' resolving for test hostname
--
Key: HADOOP-11535
URL: https://issues.apache.org/jira/browse/HADOOP-11535
Project: Hadoop Common
Issue Type: Test
Reporter: Kai Zheng
Assignee: Kai Zheng
Priority: Minor
When mvn test in my environment, it reported the following.
{noformat}
Failed tests:
TestTableMapping.testClearingCachedMappings:144 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testTableCaching:79 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testResolve:56 expected:/[rack1] but
was:/[default-rack]
{noformat}
It's caused by the good resolving for the 'bad test' hostname 'a.b.c' as
follows.
{noformat}
[drankye@zkdesk hadoop-common-project]$ ping a.b.c
PING a.b.c (220.250.64.228) 56(84) bytes of data.
{noformat}
I understand it may happen in just my local environment, and document this
just in case others also meet this. We may use even worse hostname than
'a.b.c' to avoid such situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11535) TableMapping related tests failed due to 'correct' resolving for test hostname
[
https://issues.apache.org/jira/browse/HADOOP-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303711#comment-14303711
]
Steve Loughran commented on HADOOP-11535:
-
Reserved Top Level DNS Names, RFC2606. The test should be using one of those
domains
https://tools.ietf.org/html/rfc2606
TableMapping related tests failed due to 'correct' resolving for test hostname
--
Key: HADOOP-11535
URL: https://issues.apache.org/jira/browse/HADOOP-11535
Project: Hadoop Common
Issue Type: Test
Reporter: Kai Zheng
Assignee: Kai Zheng
Priority: Minor
When mvn test in my environment, it reported the following.
{noformat}
Failed tests:
TestTableMapping.testClearingCachedMappings:144 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testTableCaching:79 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testResolve:56 expected:/[rack1] but
was:/[default-rack]
{noformat}
It's caused by the good resolving for the 'bad test' hostname 'a.b.c' as
follows.
{noformat}
[drankye@zkdesk hadoop-common-project]$ ping a.b.c
PING a.b.c (220.250.64.228) 56(84) bytes of data.
{noformat}
I understand it may happen in just my local environment, and document this
just in case others also meet this. We may use even worse hostname than
'a.b.c' to avoid such situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11535) TableMapping related tests failed due to 'correct' resolving for test hostname
[
https://issues.apache.org/jira/browse/HADOOP-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301436#comment-14301436
]
Steve Loughran commented on HADOOP-11535:
-
It's traditional to use {{something.example.org}} as the IETF mandates that
these hostnames must never resolve. However if you are using Verizon fibre @
home, it may still resolve for you. There is an implicit expectation that a
network doesn't work as defined.
TableMapping related tests failed due to 'correct' resolving for test hostname
--
Key: HADOOP-11535
URL: https://issues.apache.org/jira/browse/HADOOP-11535
Project: Hadoop Common
Issue Type: Test
Reporter: Kai Zheng
Assignee: Kai Zheng
Priority: Minor
When mvn test in my environment, it reported the following.
{noformat}
Failed tests:
TestTableMapping.testClearingCachedMappings:144 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testTableCaching:79 expected:/[rack1] but
was:/[default-rack]
TestTableMapping.testResolve:56 expected:/[rack1] but
was:/[default-rack]
{noformat}
It's caused by the good resolving for the 'bad test' hostname 'a.b.c' as
follows.
{noformat}
[drankye@zkdesk hadoop-common-project]$ ping a.b.c
PING a.b.c (220.250.64.228) 56(84) bytes of data.
{noformat}
I understand it may happen in just my local environment, and document this
just in case others also meet this. We may use even worse hostname than
'a.b.c' to avoid such situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
