[
https://issues.apache.org/jira/browse/HBASE-16519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453599#comment-15453599
]
Hudson commented on HBASE-16519:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1517 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/1517/])
HBASE-16519 Procedure v2 - Avoid sync wait on DDLs operation (addendum)
(matteo.bertozzi: rev 847955427528bb9edff44fb6b2969fc9dfd8b9cc)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManagerMetrics.java
> 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
(v6.3.4#6332)
