hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mikael Sitruk <mikael.sit...@gmail.com>
Subject Re: HMaster shutdown when a DNS address cannot be solved
Date Mon, 09 Apr 2012 21:07:59 GMT
Last minute update, the patch solved the problem.
I'm able to see my table the cluster is up now.


On Mon, Apr 9, 2012 at 10:54 PM, Mikael Sitruk <mikael.sitruk@gmail.com>wrote:

> Sorry for the late response, the issue pointed by Suraj seems similar,
> i'll try the patch a let you know.
> Amandeep sorry for the dev (I still post this issue to dev because of
> Stack), i'll pay attention to that next time. Regarding restoring the DNS
> is seems to me a wrong solution, I used a FQDNS then i shutdown the servers
> change the DNS to have only short name it should be ok. Like it is in the
> issue it can be done because of maintenance issues.
> Shashwat - the short name are ok (ping, resolving) but the long name not.
> The question is why a server try to identify itself with a long name and
> not a short name.
> In my case, the short name was always used, then one day due to another
> cluster we work with, the IT added the long name resolution to both
> clusters. i wanted to switch back to shortname, so he removed the long name
> resolution from the DNS, and now i have this problem.
> Mikael.S
> On Mon, Apr 9, 2012 at 7:02 PM, Stack <stack@duboce.net> wrote:
>> On Sun, Apr 8, 2012 at 2:37 PM, Suraj Varma <svarma.ng@gmail.com> wrote:
>> > You may be hitting this:
>> https://issues.apache.org/jira/browse/HBASE-5481
>> > --Suraj
>> >
>> Mikael:
>> Does the issue Suraj references fix your issue?
>> St.Ack

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message