Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@accumulo.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGNyuhXjJ_rhxfkjaf24R4e05YXLH9udTaRWibBh2NsSpY_+tw@mail.gmail.com>
References: 
 <CAGNyuhXjJ_rhxfkjaf24R4e05YXLH9udTaRWibBh2NsSpY_+tw@mail.gmail.com>
Date: Thu, 4 Jun 2015 22:55:55 -0400
Message-ID: 
 <CAGNyuhUrz151ce=4-nAcGPPRzuviacnsF8m5=6YJNtwE+9HFWg@mail.gmail.com>
Subject: Re: proper way to rebuild accumulo cluster
From: "Xu (Simon) Chen" <xchenum@gmail.com>
To: user@accumulo.apache.org
Content-Type: multipart/alternative; boundary=bcaec51a742c5416eb0517bc6e98

--bcaec51a742c5416eb0517bc6e98
Content-Type: text/plain; charset=UTF-8

Never mind. "stop-all.sh" and "start-all.sh" worked.

I had two master nodes, and I only rebooted one of them. Possibly the
secondary took over with stale data.

-Simon

On Thu, Jun 4, 2015 at 10:49 PM, Xu (Simon) Chen <xchenum@gmail.com> wrote:

> Hi all,
>
> I am trying to set up an accumulo cluster with kerberos support. I
> initially used password auth, therefore accumulo wasn't configured with a
> privileged kerberos principal. After I turned on kerberos, root password
> doesn't work anymore (obviously..)
>
> I then wanted to re-bootstrap my cluster - a complete rebuild is fine,
> since there isn't any valuable data. I removed /accumulo from HDFS, and
> re-ran "accumulo init". This time, I got the chance to enter a valid
> kerberos principal, which is good.
>
> Unfortunately, all the tservers stopped working after this. Looking at the
> log, it looks like the tserver is saying "ERROR: Got message from a service
> with a mismatched configuration. Please ensure a compatible configuration."
>
> Any ideas what is the proper way rebuild a cluster?
>
> Thanks.
> -Simon
>

--bcaec51a742c5416eb0517bc6e98
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Never mind. &quot;stop-all.sh&quot; and &quot;start-all.sh=
&quot; worked.=C2=A0<div><br></div><div>I had two master nodes, and I only =
rebooted one of them. Possibly the secondary took over with stale data.</di=
v><div><br></div><div>-Simon</div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Thu, Jun 4, 2015 at 10:49 PM, Xu (Simon) Chen <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:xchenum@gmail.com" target=3D"_blank">x=
chenum@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv dir=3D"ltr">Hi all,<div><br></div><div>I am trying to set up an accumulo=
 cluster with kerberos support. I initially used password auth, therefore a=
ccumulo wasn&#39;t configured with a privileged kerberos principal. After I=
 turned on kerberos, root password doesn&#39;t work anymore (obviously..)</=
div><div><br></div><div>I then wanted to re-bootstrap my cluster - a comple=
te rebuild is fine, since there isn&#39;t any valuable data. I removed /acc=
umulo from HDFS, and re-ran &quot;accumulo init&quot;. This time, I got the=
 chance to enter a valid kerberos principal, which is good.</div><div><br><=
/div><div>Unfortunately, all the tservers stopped working after this. Looki=
ng at the log, it looks like the tserver is saying &quot;ERROR: Got message=
 from a service with a mismatched configuration. Please ensure a compatible=
 configuration.&quot;</div><div><br></div><div>Any ideas what is the proper=
 way rebuild a cluster?</div><div><br></div><div>Thanks.</div><span class=
=3D"HOEnZb"><font color=3D"#888888"><div>-Simon</div></font></span></div>
</blockquote></div><br></div>

--bcaec51a742c5416eb0517bc6e98--