hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Bertozzi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10926) Use global procedure to flush table memstore cache
Date Fri, 13 Jun 2014 12:56:02 GMT

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

Matteo Bertozzi commented on HBASE-10926:
-----------------------------------------

{quote}But on the other hand, we don't 'watch' for the parent 'root' path on the coordinator
side, we only 'watch' for the expected member path. Right?{quote}
The watcher is on the ProcedureCoordinator not on the members. 
we have a single watcher for all the acquired/reached/abort events.
so we get the parent events too

> Use global procedure to flush table memstore cache
> --------------------------------------------------
>
>                 Key: HBASE-10926
>                 URL: https://issues.apache.org/jira/browse/HBASE-10926
>             Project: HBase
>          Issue Type: Improvement
>          Components: Admin
>    Affects Versions: 0.96.2, 0.98.1
>            Reporter: Jerry He
>            Assignee: Jerry He
>             Fix For: 0.99.0
>
>         Attachments: HBASE-10926-trunk-v1.patch, HBASE-10926-trunk-v2.patch, HBASE-10926-trunk-v3.patch,
HBASE-10926-trunk-v4.patch
>
>
> Currently, user can trigger table flush through hbase shell or HBaseAdmin API.  To flush
the table cache, each region server hosting the regions is contacted and flushed sequentially,
which is less efficient.
> In HBase snapshot global procedure is used to coordinate and flush the regions in a distributed
way.
> Let's provide a distributed table flush for general use.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message