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-13571) Procedure v2 - client modify table sync
Date Sat, 09 May 2015 00:19:00 GMT

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

Matteo Bertozzi commented on HBASE-13571:
-----------------------------------------

I don't think it will make any difference on AM implementation, we may get rid of it on rewrite
because it will be something we have for free but that's another story.

this change is probably only user semantic. in theory if you ask for a sync modify you expect
that once it returns every RS has the change so any of bulkreopen sync or client-side wait
on getAlterStatus() sounds good to me

> Procedure v2 - client modify table sync
> ---------------------------------------
>
>                 Key: HBASE-13571
>                 URL: https://issues.apache.org/jira/browse/HBASE-13571
>             Project: HBase
>          Issue Type: Sub-task
>          Components: proc-v2
>            Reporter: Srikanth Srungarapu
>            Assignee: Srikanth Srungarapu
>            Priority: Minor
>         Attachments: HBASE-13571.patch
>
>
> Client side part of HBASE-13210. 
> It uses the new procedure code to be know when the procedure is completed, and have a
proper sync/async behavior on modify table.



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

Mime
View raw message