[
https://issues.apache.org/jira/browse/HBASE-20658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508988#comment-16508988
]
Ankit Singhal commented on HBASE-20658:
---------------------------------------
bq. Truncate was a synchronous operation
Yes, just checked that 1.x expects it to be synchronous.
bq. However, modify table was an async operation so that reason doesn't hold
for it. However, as you see, we added the synchronous lock for HBASE-19953. I
did leave a comment which might be relevant.
The comment actually talks about releasing a latch after performing some
pre-check which is true for all other procedures except these two(where the
latch is released at the end), so was not sure that it was an oversight or done
purposely?
> Release latch early for ModifyTable and TruncateTable procedure.
> ----------------------------------------------------------------
>
> Key: HBASE-20658
> URL: https://issues.apache.org/jira/browse/HBASE-20658
> Project: HBase
> Issue Type: Bug
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Priority: Major
>
> It seems we are releasing latch in Modify and Truncate table procedures
> during completion cleanup which make the whole procedure to execute
> synchronously.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
