Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of nazario.lucas@gmail.com
 designates 209.85.160.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=imcn2YS7xA0Hlr2yG36P4gAgaTSJYPXSZeZwcRxVFxqDXA+GaJvjmioCD8s9/08BBi
         lxeetDoRbsUP5Y+x/X8smzTl+YhNKzl9Cxd3Svf80ZvqtuNqNKkzcQMH3znS0s+/mrZ9
         O3sYieSC3PN/uVpPh9bM62v8V4dYFUiu/ETSY=
MIME-Version: 1.0
In-Reply-To: <AANLkTikqHoOujMU3kFgvpdzRgJJCrSsq_v9VFoDDeslK@mail.gmail.com>
References: <AANLkTim7NjOEQs8ExyXnuPXYrnkDfBt0nJUU90CcgdOM@mail.gmail.com>
	<AANLkTikjPIYgERf7F6yOEMqPD6YQt4sgyI8jdWyPY-lb@mail.gmail.com>
	<AANLkTimKxDouGHmTfHYbYFtT1zlnD-5who8X56dTXP_R@mail.gmail.com>
	<4BFED498.5020408@apache.org>
	<AANLkTimkaqR5-Ya4rbTpycpcaUifrUrugm2pNUA8f6hc@mail.gmail.com>
	<AANLkTilFCmIwtgnyRtdSHf-J3uu6JLSjG0GMxZxBuNPG@mail.gmail.com>
	<AANLkTilW1hT3-ywwKca-JFJgv4is1DNfuXXcu-KuMxy2@mail.gmail.com>
	<AANLkTikqHoOujMU3kFgvpdzRgJJCrSsq_v9VFoDDeslK@mail.gmail.com>
Date: Fri, 28 May 2010 14:08:04 -0300
Message-ID: <AANLkTimitF40xr-PZp-tSALAorHS9kwr0uaObU92yBYx@mail.gmail.com>
Subject: Re: Zookeeper apparently going down
From: =?ISO-8859-1?Q?Lucas_Naz=E1rio_dos_Santos?= <nazario.lucas@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=000e0cd35abce2ec420487aa8c4a

--000e0cd35abce2ec420487aa8c4a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I restarted the process and the logs are gone. I'll keep monitoring HBase
and if this error happen once again I post the logs here.

Thanks a lot.

Lucas


On Fri, May 28, 2010 at 1:50 PM, Jean-Daniel Cryans <jdcryans@apache.org>wr=
ote:

> Yeah this is very suspicious. Also since the error the master tripped
> over happened just after the region server stopped logging in that
> file seems even more suspicious. Usually when there's an error in the
> regionserver's main thread it will go to sysout so that's the .out
> file instead of .log file, but every time you restart a process it
> overwrites it, so unless you didn't restart the region server we
> probably lost the info that were in there. And if the process did die,
> then it really explains why the master wasn't able to connect to it.
>
> J-D
>
> On Fri, May 28, 2010 at 8:37 AM, Lucas Naz=E1rio dos Santos
> <nazario.lucas@gmail.com> wrote:
> > Here are the complete logs:
> >
> >
> http://www.ninvest.com.br/docs/logs_hbase/hbase-root-master-ip-10-251-158=
-224.log
> >
> http://www.ninvest.com.br/docs/logs_hbase/hbase-root-zookeeper-ip-10-251-=
158-224.log
> >
> http://www.ninvest.com.br/docs/logs_hbase/hbase-root-regionserver-ip-10-2=
51-158-224.log
> >
> > The regionserver stopped logging at 8:31am. Strange...
> >
> > I hope this help.
> >
> > Lucas
> >
> >
> > On Thu, May 27, 2010 at 8:09 PM, Jean-Daniel Cryans <jdcryans@apache.or=
g
> >wrote:
> >
> >> On Thu, May 27, 2010 at 4:01 PM, Lucas Naz=E1rio dos Santos
> >> <nazario.lucas@gmail.com> wrote:
> >> > Thanks a lot for the responses. I'll be monitoring HBase and get bac=
k
> in
> >> > touch if it happens again.
> >> >
> >> > Maybe HBase could employ a mechanism to automatically recover from
> >> > connectivity issues like the one I had gone through. Then me and
> others
> >> > wouldn't need to manually restart it.
> >>
> >> Well usually if one machine is not reachable, it's not a big deal
> >> since there are other machines to connect to and HBase redistributes
> >> the regions to them. Also, why is it refused? Can we see the region
> >> server log?
> >>
> >> >
> >> > I still didn't get why the master kept failing even after its
> recovery,
> >> and
> >> > why I had to stop/start the cluster in order to get rid of the
> >> "Connection
> >> > refused" error.
> >>
> >> I'd also like to understand why the region server isn't responding,
> >> the master can only know so much.
> >>
> >> >
> >> > I'm assuming it's not big deal and my solution can live with it.
> >> >
> >> > More logs bellow.
> >> >
> >>
> >> Consider pastebin or a web server next time ;)
> >>
> >
>

--000e0cd35abce2ec420487aa8c4a--