Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 8 Oct 2015 14:25:26 +0000 (UTC)
From: "Eric Newton (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12903349.1444310067000.56988.1444314326800@Atlassian.JIRA>
In-Reply-To: <JIRA.12903349.1444310067000@Atlassian.JIRA>
References: <JIRA.12903349.1444310067000@Atlassian.JIRA>
 <JIRA.12903349.1444310067490@arcas>
Subject: [jira] [Comment Edited] (ACCUMULO-4022) Create a concept of
 multi-homed tablets
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Newton edited comment on ACCUMULO-4022 at 10/8/15 2:25 PM:
----------------------------------------------------------------

In HBase, this is a feature referred to as Region Replicas. Implemented not too long ago. I'm sure you can find a design doc.


was (Author: elserj):
In HBase, this is a feature referred to as Region Replicas. Not implemented too long ago. I'm sure you can find a design doc.

> Create a concept of multi-homed tablets
> ---------------------------------------
>
>                 Key: ACCUMULO-4022
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4022
>             Project: Accumulo
>          Issue Type: Wish
>          Components: client, tserver
>            Reporter: marco polo
>              Labels: newbie, performance
>
> I'm an accumulo newbie, but I wish to see the concept of multi-homed tablets. This allows us to have tablets hosted by multiple servers, with only one being writable against it. This concept would allow n receiver servers for a tablet. An example might be a tablet that has become a hot spot could be dynamically hosted elsewhere, and clients could pick this up as a potential. Consistency must be kept between the hosts, as the initial read/write host may compact or write to that tablet. 
> To me the larger problem may come from live ingest in which the write ahead log has not been flushed. To avoid having to write to the read only servers in a pipeline, we would likely need to create a model of enforcing reads only after a flush of that tablet or a thrift interface to allow reading only the data in memory to ensure consistency is enforced. I haven't given great thought to solving this yet. 
> Please comment with ideas and pitfalls as I would like to see this wish come to fruition with actionable tickets after some community thought.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)