Correct, but settings hbase.regionserver.hostname should be enough if I
remember correctly, also you need to define hbase.master.hostname if you
are using HBase 1.1
cheers,
esteban.
--
Cloudera, Inc.
On Fri, May 22, 2015 at 12:55 PM, Bryan Beaudreault
bbeaudrea...@hubspot.com wrote:
Thanks
Bryan:
HBASE-12954 introduced config for region server hostname.
The following added config for master hostname:
HBASE-13481 Master should respect master (old) DNS/bind related
configurations
I will link the above JIRA to HBASE-12954
Cheers
On Fri, May 22, 2015 at 12:55 PM, Bryan Beaudreault
On Fri, May 22, 2015 at 2:34 PM, Ted Yu yuzhih...@gmail.com wrote:
bq. hbase-1.1.0.1
To my knowledge, latest release was 1.1.0. The release before that was
1.0.1
Can you clarify ?
Thanks
The 1.1.0.1 release votes all passed. I don't think the announcement has
gone out yet because we
Thank you guys for the help. I'm reading through the comments now to try to
get a handle on why this changed.
Looking forward to seeing HBASE-12954 in CDH5.4.3
On Fri, May 22, 2015 at 4:02 PM, Esteban Gutierrez este...@cloudera.com
wrote:
Correct, but settings hbase.regionserver.hostname
There's always some delay between when release artifacts are sent onward to
the mirrors and when the announcements go out, for various reasons. We made
three patch releases this week. I have it on good authority the
announcements for the current crop of releases will go out this coming
Monday.
HBASE-12954 looks like it would solve my issue, but is not in cdh5.4.0. I
also don't think it fixes what I think the real bug is -- it's more of a
workaround.
In terms of the actual bug, I think one of at least two possible solutions
should be considered:
1. Remove the support for
Thanks Esteban. So the idea is you set hbase.master.dns.* on the master
side, and hbase.regionserver.hostname to a value matching what the master
DNS server would return on the regionserver side?
On Fri, May 22, 2015 at 3:51 PM, Esteban Gutierrez este...@cloudera.com
wrote:
Hi Bryan,
The
On Fri, May 22, 2015 at 10:17 AM, Bryan Beaudreault
bbeaudrea...@hubspot.com wrote:
In our system each server has 2 dns associated with it, one always points
to a private address and the other to public or private depending on the
context.
This issue did not show up in 0.94.x, but is
On Fri, May 22, 2015 at 10:12 PM, Stack st...@duboce.net wrote:
On Fri, May 22, 2015 at 10:17 AM, Bryan Beaudreault
bbeaudrea...@hubspot.com wrote:
In our system each server has 2 dns associated with it, one always points
to a private address and the other to public or private depending on
In our system each server has 2 dns associated with it, one always points
to a private address and the other to public or private depending on the
context.
This issue did not show up in 0.94.x, but is showing up on my new 1.x
cluster. Basically it goes like this:
1. Regionserver starts up,
Hi Bryan,
could you please be more specific about the 1.x version that you are using?
we have HBASE-13481 and HBASE-12954 so it depends on which version of 1.x
you are using.
Regarding your account issue, I have created an INFRA JIRA on your behalf
to look into your account problem.
thanks,
Thank you Esteban. I checked two different versions:
- hbase-1.0.0-cdh5.4.0 (this is the version I use)
- hbase-1.1.0.1 (just wanted to check the latest release)
On Fri, May 22, 2015 at 3:13 PM, Esteban Gutierrez este...@cloudera.com
wrote:
Hi Bryan,
could you please be more specific about
bq. hbase-1.1.0.1
To my knowledge, latest release was 1.1.0. The release before that was 1.0.1
Can you clarify ?
Thanks
On Fri, May 22, 2015 at 12:23 PM, Bryan Beaudreault
bbeaudrea...@hubspot.com wrote:
Thank you Esteban. I checked two different versions:
- hbase-1.0.0-cdh5.4.0 (this is
13 matches
Mail list logo
