Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6CF0B1137B for ; Thu, 10 Jul 2014 13:19:57 +0000 (UTC) Received: (qmail 50752 invoked by uid 500); 10 Jul 2014 13:19:57 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 50703 invoked by uid 500); 10 Jul 2014 13:19:57 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 50686 invoked by uid 99); 10 Jul 2014 13:19:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jul 2014 13:19:57 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of awells@clearedgeit.com designates 209.85.214.181 as permitted sender) Received: from [209.85.214.181] (HELO mail-ob0-f181.google.com) (209.85.214.181) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jul 2014 13:19:54 +0000 Received: by mail-ob0-f181.google.com with SMTP id wp4so9897124obc.12 for ; Thu, 10 Jul 2014 06:19:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=W3/bUAHI3/p3xSmPV2zvid3l7TGWWi9gCj7tS4xCeJ8=; b=ds36BS0l32mZ0lUhjyHSxyuUedq45MCpcXW4QdPxWysUCGIbGM2R+NrZJuJLqQhVun RZp+OE9PeT4UZGZA0OTs467Fw/DnNF7iYIb1Y0eni91tSRBN0d4/mdsg/PPADhLJ0t3u Ei5ajATRsizHjs/XMgnnUBq8ekJsRxIX3zHfDWoTxRhjUXUn0MEd8mThq/zBnGwN8SAJ LPVRxEocSvuD5lCJ8EqimEt63cAKW//Zl70HBQIpEpE8xxXZ/6jGDWKA3UI2FVbVXU5y iF9Yv5BwiSHphRUHZteimHvyZ48sXrsc1xqhWKORi4JstJc6L010UM8h5e7UJAqRWkNf x+Wg== X-Gm-Message-State: ALoCoQkj1BXFnwD6xMjllxo7LUaT98QOTXgcJlyJH/R8fFrvslh1X3Usg/PEpJMX6LLhZ2n6+t8Q X-Received: by 10.60.80.229 with SMTP id u5mr24619222oex.62.1404998369708; Thu, 10 Jul 2014 06:19:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.229.7 with HTTP; Thu, 10 Jul 2014 06:19:09 -0700 (PDT) In-Reply-To: References: From: Andrew Wells Date: Thu, 10 Jul 2014 09:19:09 -0400 Message-ID: Subject: Re: Definition of System Status' To: user@accumulo.apache.org Content-Type: multipart/alternative; boundary=089e013cbcc6bca6b904fdd6ac98 X-Virus-Checked: Checked by ClamAV on apache.org --089e013cbcc6bca6b904fdd6ac98 Content-Type: text/plain; charset=UTF-8 On Thu, Jul 10, 2014 at 9:04 AM, Eric Newton wrote: > > > > On Thu, Jul 10, 2014 at 8:47 AM, Andrew Wells > wrote: > >> I am working for a client, and they keep getting TABLET_LOAD problems. >> > > Okay. > > >> >> I am assuming it means that the tablet is being overloaded, but there >> really isn't any definition of what this means, or its cause. >> > > No, it means there is a problem loading the tablet. The master has > assigned it, and the tablet server is having trouble loading it. > > One possible problem is that the files for the tablet are missing. > Another might be a missing or corrupt recovery log. > > These are serious errors. > This is the kind of information we need in the administrators guide > > > >> This also goes for other problem statuses like FiILE_READ FILE_WRITE >> > > These should be accompanied by messages about the files in question. > > Under heavy load, HDFS read/write errors will bubble up to accumulo, and > it will post these errors. > Same as top. Do you (or anyone reading) know of common configuration problems that cause this? Resolutions? > > >> >> As accumulo get bigger, we may want to have a dictionary of Problem >> Status, Problems, and Resolutions >> > > A dictionary should probably have, types of errors/warnings, definitions, >> common problems and resolutions. >> > > Have you read the troubleshooting section of the user's manual? If there > is something you would like to see there, make a ticket: > I read google, the only thing i found was something written by billie. > > https://issues.apache.org/jira/browse/ACCUMULO/ > > As always, contributions are welcome. > I'll try to make some tickets tonight. If people don't mind listing definitions of status as well as generic problems and solutions in this thread, I could reference this email chain in the ticket as a resource. > > > > -Eric > -- *Andrew George Wells* *Software Engineer* *awells@clearedgeit.com * --089e013cbcc6bca6b904fdd6ac98 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



On Thu, Jul 10, 2014 at 9:04 AM, Eric Newton <= eric.newton@gmai= l.com> wrote:



On Thu, Jul 10, 2014= at 8:47 AM, Andrew Wells <awells@clearedgeit.com> wrot= e:
I am wor= king for a client, and they keep getting TABLET_LOAD problems.

Okay.
=C2=A0
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">

=
I am assuming it means that the tablet is being overloaded, but there reall= y isn't any definition of what this means, or its cause.=C2=A0

No, it means there is a = problem loading the tablet.=C2=A0 The master has assigned it, and the table= t server is having trouble loading it.

One possible probl= em is that the files for the tablet are missing.=C2=A0 Another might be a m= issing or corrupt recovery log.

These are serious errors.
=C2=A0
This is the kind of information we need in the admi= nistrators guide=C2=A0
=C2=A0
=
=C2=A0
This also goes for other problem statuses like FiILE_READ F= ILE_WRITE

These sho= uld be accompanied by messages about the files in question.

Under heavy load, HDFS read/write errors will bubble up to accumulo, and it= will post these errors.
Same = as top. Do you (or anyone reading) know of common configuration problems th= at cause this? Resolutions?
=
=C2=A0

As accumulo get bigger, we may wa= nt to have a dictionary of Problem Status, Problems, and Resolutions
<= /div>

A dictionary should probably have, types of erro= rs/warnings, definitions, common problems and resolutions.

Have you read the troubleshooting s= ection of the user's manual?=C2=A0 If there is something you would like= to see there, make a ticket:
I read google, the only thing i f= ound was something written by billie.=C2=A0


As always, contributions are welcom= e.

I'll try to make som= e tickets tonight. If people don't mind listing definitions of status a= s well as generic problems and solutions in this thread, I could reference = this email chain in the ticket as a resource.=C2=A0
=
=C2=A0
=


-Eric



--
Andrew George Wells
Software Engineer
--089e013cbcc6bca6b904fdd6ac98--