[
https://issues.apache.org/jira/browse/ACCUMULO-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026622#comment-14026622
]
Josh Elser commented on ACCUMULO-1495:
--------------------------------------
I think over query performance, this would be more noticeable in improving
MTTR. If we have multiple tservers that are hosting a tablet for reads, you
still have ways to get that data that don't involve waiting for recovery to
complete.
HBase has been doing a lot of work in this department as of late to be able to
provide better SLAs.
https://issues.apache.org/jira/browse/HBASE-10070
http://www.slideshare.net/enissoz/hbase-high-availability-for-reads-with-time
> Host multiple read-only versions of tablets for query performance
> -----------------------------------------------------------------
>
> Key: ACCUMULO-1495
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1495
> Project: Accumulo
> Issue Type: New Feature
> Reporter: Christopher Tubbs
>
> It might be worth providing read-only views of tablets on multiple servers,
> while writes go to a single authoritative server. This could improve query
> performance in some cases.
> Some things to consider:
> # Consistency: can I read what I've just written?
> # Configuration: how many copies?
> # Configuration: how long between syncs?
> # Performance: locality, number of file replicas
> Variation:
> Permit multiple hosting only on tables that have been locked for writes
> (useful with a strictly enforced clone-and-lock feature).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
