Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 23 May 2013 21:55:20 +0000 (UTC)
From: "Mike Drob (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12648954.1369251535017.14009.1369346120365@arcas>
In-Reply-To: <JIRA.12648954.1369251535017@arcas>
References: <JIRA.12648954.1369251535017@arcas>
Subject: [jira] [Commented] (ACCUMULO-1453) Track tablet migrations and
 failed loads
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665727#comment-13665727 ] 

Mike Drob commented on ACCUMULO-1453:
-------------------------------------

Large entries aren't the only problem - large indices can be real bad too.
                
> Track tablet migrations and failed loads
> ----------------------------------------
>
>                 Key: ACCUMULO-1453
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1453
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master, tserver
>    Affects Versions: 1.5.0, 1.4.3
>            Reporter: Mike Drob
>
> If a bad RFile or Tablet somehow gets in the system and brings down a tserver, then as the master migrates it to other servers it will likely cause cascading failures.
> It might be a good idea to keep track of how many consecutive failures to load there are for a given tablet, and either warn or refuse to host the tablet if this value exceeds a given threshold.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira