hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12954) Ability impaired using HBase on multihomed hosts
Date Tue, 31 Mar 2015 16:21:56 GMT

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

Hadoop QA commented on HBASE-12954:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12708435/12954-branch-1-v14.txt
  against branch-1 branch at commit f1f4b6618334767d0da0f47965309b21676e7e9f.
  ATTACHMENT ID: 12708435

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

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

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions
(2.4.1 2.5.2 2.6.0)

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

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

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

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number
of checkstyle errors

    {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:red}-1 lineLengths{color}.  The patch introduces the following lines longer than
100:
    +    <description>This config is for experts: don't set its value unless you really
know what you are doing.
+    When set to a non-empty value, this represents the (external facing) hostname for the
underlying server.
+              new java.lang.String[] { "Port", "ServerStartCode", "ServerCurrentTime", "UseThisHostnameInstead",
});

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

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

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/13506//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/13506//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/13506//artifact/patchprocess/checkstyle-aggregate.html

  Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/13506//console

This message is automatically generated.

> Ability impaired using HBase on multihomed hosts
> ------------------------------------------------
>
>                 Key: HBASE-12954
>                 URL: https://issues.apache.org/jira/browse/HBASE-12954
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.4
>            Reporter: Clay B.
>            Assignee: Ted Yu
>            Priority: Minor
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: 12954-branch-1-v14.txt, 12954-v1.txt, 12954-v10.txt, 12954-v11.txt,
12954-v12.txt, 12954-v12.txt, 12954-v12.txt, 12954-v13.txt, 12954-v14.txt, 12954-v7.txt, 12954-v8.txt,
Hadoop Three Interfaces.png
>
>
> For HBase clusters running on unusual networks (such as NAT'd cloud environments or physical
machines with multiple IP's per network interface) it would be ideal to have a way to both
specify:
> # which IP interface to which HBase master or region-server will bind
> # what hostname HBase will advertise in Zookeeper both for a master or region-server
process
> While efforts such as HBASE-8640 go a long way to normalize these two sources of information,
it is not possible in the current design of the properties available to an administrator for
these to be unambiguously specified.
> One has been able to request {{hbase.master.ipc.address}} or {{hbase.regionserver.ipc.address}}
but one can not specify the desired HBase {{hbase.master.hostname}}. (It was removed in HBASE-1357,
further I am unaware of a region-server equivalent.)
> I use a configuration management system to generate all of my configuration files on
a per-machine basis. As such, an option to generate a file specifying exactly which hostname
to use would be helpful.
> Today, specifying the bind address for HBase works and one can use an HBase-only DNS
for faking what to put in Zookeeper but this is far from ideal. Network interfaces have no
intrinsic IP address, nor hostname. Specifing a DNS server is awkward as the DNS server may
differ from the system's resolver and is a single IP address. Similarly, on hosts which use
a transient VIP (e.g. through keepalived) for other services, it means there's a seemingly
non-deterministic hostname choice made by HBase depending on the state of the VIP at daemon
start-up time.
> I will attach two networking examples I use which become very difficult to manage under
the current properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message