hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Bertozzi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-16519) Procedure v2 - Avoid sync wait on DDLs operation
Date Fri, 02 Sep 2016 16:24:22 GMT

     [ https://issues.apache.org/jira/browse/HBASE-16519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matteo Bertozzi resolved HBASE-16519.
    Resolution: Fixed

> Procedure v2 - Avoid sync wait on DDLs operation
> ------------------------------------------------
>                 Key: HBASE-16519
>                 URL: https://issues.apache.org/jira/browse/HBASE-16519
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master, proc-v2
>    Affects Versions: 2.0.0
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>             Fix For: 2.0.0
>         Attachments: HBASE-16519-addendum.patch, HBASE-16519-v0.patch
> Some operation ModifyColumnFamily, AddDeleteColumnFamily, DeleteColumnFamily, ModifyTable,
TruncateTable are still synchronous on the master side. with a wait until the operation completes
before returning. 
> this was done to keep the sync behavior for old client. but instead of using the procLatch
which recognize the client version and decide if the operation should be sync or not it just
always wait. making the client side proc fault tolerance ineffective.
> also the add/delete/modifyColumnFamily operation does not seems to follow the Async()
naming in master. and the comment claim to be async but everyone uses them as sync. (this
is something from HBASE-13538)

This message was sent by Atlassian JIRA

View raw message