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

Appy updated HBASE-19457:
-------------------------
    Description: 
Trying to explain the bug in a more general way where understanding of 
ProcedureV2 is not required.

Truncating table operation:
....
delete region states from meta
delete table state from meta
....
add new regions to meta with state null.
....crash
....recovery: TableStateManager treats table with null state as ENABLED. AM 
treats regions with null state as offline. Combined result - AM starts 
assigning the new regions from incomplete truncate operation.

Fix: Mark table as disabled instead of deleting it's state.
----
*patch1*
Just added some logging to help with debugging:
- 60s was too less time, increased timeout
- Added some useful log statements


  was:



*patch1*
- 60s was too less time, increased timeout
- Added some useful log statements



> Debugging flaky 
> TestTruncateTableProcedure#testRecoveryAndDoubleExecutionPreserveSplits
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-19457
>                 URL: https://issues.apache.org/jira/browse/HBASE-19457
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Appy
>            Assignee: Appy
>         Attachments: HBASE-19457.master.001.patch, patch1, test-output.txt
>
>
> Trying to explain the bug in a more general way where understanding of 
> ProcedureV2 is not required.
> Truncating table operation:
> ....
> delete region states from meta
> delete table state from meta
> ....
> add new regions to meta with state null.
> ....crash
> ....recovery: TableStateManager treats table with null state as ENABLED. AM 
> treats regions with null state as offline. Combined result - AM starts 
> assigning the new regions from incomplete truncate operation.
> Fix: Mark table as disabled instead of deleting it's state.
> ----
> *patch1*
> Just added some logging to help with debugging:
> - 60s was too less time, increased timeout
> - Added some useful log statements



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to