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

Hudson commented on PHOENIX-1289:
---------------------------------

FAILURE: Integrated in Phoenix | Master #403 (See 
[https://builds.apache.org/job/Phoenix-master/403/])
PHOENIX-1289 Drop index during upsert may abort RS (daniel meng + jyates) 
(jyates: rev faeab935554404a042285a01127e9b88b8e3a47c)
* 
phoenix-core/src/main/java/org/apache/phoenix/index/PhoenixIndexFailurePolicy.java
* 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/write/KillServerOnFailurePolicy.java
* 
phoenix-core/src/it/java/org/apache/phoenix/end2end/index/DropIndexDuringUpsertIT.java


> 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
>            Assignee: daniel meng
>             Fix For: 5.0.0, 4.2
>
>         Attachments: DropIndexDuringUpsertIT.java, PHOENIX-1289.PATCH, 
> phoenix-1289-v1.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)

Reply via email to