[
https://issues.apache.org/jira/browse/HBASE-20642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508792#comment-16508792
]
Josh Elser commented on HBASE-20642:
------------------------------------
{quote}if we fix HBASE-20658 by releasing the latch after some pre-checks for
Modify and Truncate table , then probably we may not need to do nonce check as
retry mechanism will not kick in if the procedure is submitted successfully.
{quote}
I think in both cases, we don't want to release those latches early (would
break functionality of Truncate, and regress on HBASE-19953 for modify table).
However, using the same nonce from the client seems like the right fix to me.
We have _one_ client and this client is (unwittingly) submitting the same
procedure multiple times. I don't think I've seen any reason that this should
be using a new nonce – so let's make the nonce help us in this known-deficient
case :)
> IntegrationTestDDLMasterFailover throws 'InvalidFamilyOperationException
> -------------------------------------------------------------------------
>
> Key: HBASE-20642
> URL: https://issues.apache.org/jira/browse/HBASE-20642
> Project: HBase
> Issue Type: Bug
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Priority: Major
> Attachments: HBASE-20642.patch
>
>
> [~romil.choksi] reported that IntegrationTestDDLMasterFailover is failing
> while adding column family during the time master is restarting.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
