You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Jesse Yates (JIRA)" <ji...@apache.org> on 2014/10/01 01:52:34 UTC
[jira] [Comment Edited] (PHOENIX-1289) Drop index during upsert may
abort RS
[ https://issues.apache.org/jira/browse/PHOENIX-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150896#comment-14150896 ]
Jesse Yates edited comment on PHOENIX-1289 at 9/30/14 11:52 PM:
----------------------------------------------------------------
[~jesse_yates] it' seems strange for me, here is what i'm understand after some debugging: there is only one index "S.I" in the unit test , so the first parameter in
{code}
handlerFailure(Multimap<HTableInterfaceReference, Mutation> attempted, Exception cause)
{code}
should only has one entry for S.I , and then there will be no loop. i can not understand why " indexTableNames.clear(); is necessary ", it always goes right on my side.
was (Author: daniel.m):
[~jesse_yates] it' seems strange for me, here is what i'm understand after some debugging: there is only one index "S.I" in the unit test , so the first parameter in
```java
handlerFailure(Multimap<HTableInterfaceReference, Mutation> attempted, Exception cause)
```
should only has one entry for S.I , and then there will be no loop. i can not understand why " indexTableNames.clear(); is necessary ", it always goes right on my side.
> Drop index during upsert may abort RS
> -------------------------------------
>
> Key: PHOENIX-1289
> URL: https://issues.apache.org/jira/browse/PHOENIX-1289
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: daniel meng
> Attachments: DropIndexDuringUpsertIT.java, PHOENIX-1289.PATCH
>
>
> below execute path will abort RS:
> 1. client A write to table T with mutation m。 and T has an index of name IDX
> 2. m arrival at RS, but not start processing yet
> 3. client B drop index IDX
> 4. RS try to process m, and we get m' for IDX
> 5. RS try to write m' but fail as HBase Table IDX not exist
> 6. RS try to disable IDX but fail as Metadata has been deleted
> 7. KillServerOnFailurePolicy is triggered, server abort
> 8. recovery will fail with the same reason.
> an IT is attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)