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

Stephen Yuan Jiang commented on HBASE-14051:
--------------------------------------------

[~enis] no, the workaround in enable/disable table was for failover - once 
failover, part of recovery code would complete enable/disable tables if the 
table is in the middle of enabling/disabling (see 
AssignmentManager#recoverTableInDisablingState() and 
recoverTableInEnablingState()) - the nonce would not help, as the recovery code 
issue a different enable/disable request and are not aware of the procedure 
from the client.  HBASE-13823 would remove this redundant recovery (to be safe, 
it would be part of AM rewrite; not a simple cleanup/remove).  

> Undo workarounds in IntegrationTestDDLMasterFailover for client double submit
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-14051
>                 URL: https://issues.apache.org/jira/browse/HBASE-14051
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master
>            Reporter: Enis Soztutar
>            Assignee: Sophia Feng
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>
>         Attachments: HBASE-14051.v1.patch
>
>
> Now that nonce support for dealing with double-submits from client in 
> HBASE-13415 is committed, we should undo the workarounds done in HBASE-13470 
> for this part. We needed these workarounds for 1.1.1, but we should not do 
> that anymore for proper testing for 1.2+. 
> [~syuanjiang], [~fengs], [~mbertozzi] FYI. 



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

Reply via email to