Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@accumulo.apache.org
Received-SPF: pass (nike.apache.org: domain of padraigdidanan@gmail.com
 designates 209.85.219.54 as permitted sender)
MIME-Version: 1.0
From: Dave Mullins <padraigdidanan@gmail.com>
Date: Fri, 1 Nov 2013 16:17:53 -0400
Message-ID: 
 <CAD1oDtfdFeum0Ozkb86sJAf=qAMnfyNN+mK0-76GuPaWhknjaQ@mail.gmail.com>
Subject: Accumulo Upgrade from 1.4.2 to 1.5.0 Issues
To: user@accumulo.apache.org
Content-Type: multipart/alternative; boundary=089e01175e4d0b054604ea234477

--089e01175e4d0b054604ea234477
Content-Type: text/plain; charset=ISO-8859-1

Hadoop version 0.20.2-cdh3u5
This was installed from the cdh rpms but is not controlled by a cloudera
manager.

I read what documentation I could find on the upgrade.
I installed from the tarball version of 1.5.0.
I made sure to include the commons collection in the accumulo library path.
I made sure to add the dfs.support.append true to the hdfs-site files.
I did a complete restart ( to include a reboot) of the system.

All of the tablet servers come online
all the master's services come online and seem to be working. (The monitor
does show the correct number of tablets, tablet servers, and so forth.)

I am able to use some of the features of the accumulo shell
I can display the contents of a table.
I can't create or delete a table without getting the following error:
[impl.ThriftTransportPool] WARN: Thread "shell" stuck on io to
x.x.x.x:9999:9999 (0) for at least 120040 ms

When I go digging in the logs I find very few errors. (These systems are
not on a net I can cut and paste to here so I am trying to represent the
issue as best I can.)

There are 4 errors that the Repo runner [0-3] threads died

Another error that springs up occasionally is : WARN: Thread "GC" stuck on
io to x.x.x.x:9999:9999 (0) for at least 120040 ms

A netstat run before I start the master up shows nothing running on port
9999 nor any connections to that port.
A netstat after about the accumulo start shows about 16 connections in a
TIME_WAIT state in the 35k-36k port range from the master. It also show an
established state for 1 both both direction (36783) and inbound from port
9999 to port 47636 also from the master.

It seems after this point anything that tries to connect to port 9999 goes
into a TIME_WAIT and never does anything.

I have checked all the permissions I can think of and everything seems to
be correct.
HDFS is running correctly and jobs not associated with accumulo all see to
be working.

--089e01175e4d0b054604ea234477
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hadoop version 0.20.2-cdh3u5 <br></div>This was insta=
lled from the cdh rpms but is not controlled by a cloudera manager.<br><div=
>=A0<br>I read what documentation I could find on the upgrade. <br></div><d=
iv>


I installed from the tarball version of 1.5.0.<br></div><div>I made sure to=
 include the commons collection in the accumulo library path.<br></div><div=
>I made sure to add the dfs.support.append true to the hdfs-site files.<br>


</div><div>I did a complete restart ( to include a reboot) of the system.<b=
r><br></div><div>All of the tablet servers come online<br></div><div>all
 the master&#39;s services come online and seem to be working. (The monitor=
=20
does show the correct number of tablets, tablet servers, and so forth.)<br>
<br></div><div>I am able to use some of the features of the accumulo shell<=
br></div><div>I can display the contents of a table.<br>I can&#39;t create =
or delete a table without getting the following error:<br></div><div>[impl.=
ThriftTransportPool] WARN: Thread &quot;shell&quot; stuck on io to x.x.x.x:=
9999:9999 (0) for at least 120040 ms<br>


<br></div><div>When I go digging in the logs I find very few errors.=20
(These systems are not on a net I can cut and paste to here so I am=20
trying to represent the issue as best I can.)<br><br></div><div>There are 4=
 errors that the Repo runner [0-3] threads died<br>
<br>Another error that springs up occasionally is : WARN: Thread &quot;GC&q=
uot; stuck on io to x.x.x.x:9999:9999 (0) for at least 120040 ms<br><br></d=
iv><div>A netstat run before I start the master up shows nothing running on=
 port 9999 nor any connections to that port.<br>


</div><div>A netstat after about the accumulo start shows about 16=20
connections in a TIME_WAIT state in the 35k-36k port range from the=20
master. It also show an established state for 1 both both direction=20
(36783) and inbound from port 9999 to port 47636 also from the master.<br>
<br></div><div>It seems after this point anything that tries to connect to =
port 9999 goes into a TIME_WAIT and never does anything.<br><br></div><div>=
I have checked all the permissions I can think of and everything seems to b=
e correct.<br>


</div>HDFS is running correctly and jobs not associated with accumulo all s=
ee to be working.</div>

--089e01175e4d0b054604ea234477--