[jira] [Comment Edited] (ACCUMULO-4022) Create a concept of multi-homed tablets

["Christopher Tubbs (Jira)" <ji...@apache.org>]

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

Christopher Tubbs edited comment on ACCUMULO-4022 at 10/28/20, 11:18 PM:
-------------------------------------------------------------------------

Closing this stale issue. If this is still a problem, please open a new issue or PR at https://github.com/apache/accumulo


was (Author: ctubbsii):
Closing this stale issue. If this is still a problem, please open a new issue or PR at https://github.com/apache/accumulo-testing

> 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: Marc Parisi
>            Priority: Major
>              Labels: 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
(v8.3.4#803005)