phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "daniel meng (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1289) Drop index during upsert may abort RS
Date Sun, 28 Sep 2014 02:50:35 GMT


daniel meng commented on PHOENIX-1289:

[~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 
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:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: daniel meng
>         Attachments:, 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

View raw message