Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 14 Feb 2014 23:33:20 +0000 (UTC)
From: "Eric Newton (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12695085.1392327113971.47006.1392420800441@arcas>
In-Reply-To: <JIRA.12695085.1392327113971@arcas>
References: <JIRA.12695085.1392327113971@arcas>
Subject: [jira] [Commented] (ACCUMULO-2368) Addsplits to an offline table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Newton commented on ACCUMULO-2368:
---------------------------------------

Yes, but the walogs reference the old key extent.

The walog reference in the metadata table does have the id used when the data was written, so that could be used to find the old tablet.

 WALog playback would have to use this id, and it does not, at the moment.

WALog playback would have to ignore mutations that do not fit in its range any more.

The master would need a distributed write lock, like it does for merge, when doing this operation, to prevent another user from changing the state during the middle of the operation.


> Addsplits to an offline table
> -----------------------------
>
>                 Key: ACCUMULO-2368
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2368
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master
>            Reporter: John Vines
>
> Currently a table must be online to addsplits. Firstly, it's relatively slow. Secondly, it could be a LOT faster to do it to an offline table because it's just a few metadata writes per split point.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)