hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10926) Use global procedure to flush table memstore cache
Date Wed, 30 Apr 2014 18:10:18 GMT

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

Andrew Purtell commented on HBASE-10926:
----------------------------------------

{quote}
One more missing piece I need to add is the security check.
Currently preFlush() check is done on the region server security observer.
It works well originally since the RPC user from client is checked on the region server.
But now the master starts the procedure and the region server hosting the regions initiates
the flush. That means the principal is 'hbase'?
We need to add preFlush() hook on the procedure master to check CREATE, ADMIN on the table
before we start the procedure.
{quote}

Yes it is critical that this behavior is preserved or an unprivileged user can mount a denial
of service attack.

> 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
>
>
> 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