[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Release Note: The following config is added by this JIRA: hbase.regionserver.hostname 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. See https://issues.apache.org/jira/browse/HBASE-12954 for details. Caution: please make sure rolling upgrade succeeds before turning on this feature. was: The following config is added by this JIRA: hbase.regionserver.hostname 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. See https://issues.apache.org/jira/browse/HBASE-12954 for details. > 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-addendum.txt, 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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-addendum.txt > 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-addendum.txt, 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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the reviews. > 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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: (was: 12954-branch-1-v14.txt) > 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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-branch-1-v14.txt > 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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-branch-1-v14.txt > 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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Fix Version/s: 1.1.0 2.0.0 Release Note: The following config is added by this JIRA: hbase.regionserver.hostname 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. See https://issues.apache.org/jira/browse/HBASE-12954 for details. Hadoop Flags: Reviewed > 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-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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-v14.txt Patch rebased on current master branch > 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 > Attachments: 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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-v13.txt > 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 > Attachments: 12954-v1.txt, 12954-v10.txt, 12954-v11.txt, > 12954-v12.txt, 12954-v12.txt, 12954-v12.txt, 12954-v13.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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-v12.txt > 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 > Attachments: 12954-v1.txt, 12954-v10.txt, 12954-v11.txt, > 12954-v12.txt, 12954-v12.txt, 12954-v12.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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-v12.txt > 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 > Attachments: 12954-v1.txt, 12954-v10.txt, 12954-v11.txt, > 12954-v12.txt, 12954-v12.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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-v12.txt Patch v12 is rebased on master branch. > 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 > Attachments: 12954-v1.txt, 12954-v10.txt, 12954-v11.txt, > 12954-v12.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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-v11.txt Patch v11 addresses checkstyle warnings. > 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 > Attachments: 12954-v1.txt, 12954-v10.txt, 12954-v11.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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-v10.txt > 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 > Attachments: 12954-v1.txt, 12954-v10.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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-v8.txt > 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 > Attachments: 12954-v1.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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-v7.txt This is the latest patch. Several tests have been added. Mind taking a look at this to see what to improve ? Thanks > 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 > Attachments: 12954-v1.txt, 12954-v7.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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Status: Patch Available (was: Open) > 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 > Attachments: 12954-v1.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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12954: --- Attachment: 12954-v1.txt > 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 > Attachments: 12954-v1.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)
[jira] [Updated] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[ https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clay B. updated HBASE-12954: Summary: Ability impaired using HBase on multihomed hosts (was: Ability impared using HBase on multihomed hosts) > 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. >Priority: Minor > Attachments: 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)