phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5094) Index can transition from INACTIVE to ACTIVE via Phoenix Client
Date Fri, 01 Feb 2019 21:24:00 GMT

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

Hudson commented on PHOENIX-5094:
---------------------------------

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #314 (See [https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/314/])
PHOENIX-5094 increment pending disable count for index when rebuild (vincentpoon: rev 68c92df73a1d8e3fd34657aa363bdb7d5655bc66)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataRegionObserver.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/index/PhoenixIndexFailurePolicy.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/IndexUtil.java
* (add) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/IndexRebuildIncrementDisableCountIT.java


> Index can transition from INACTIVE to ACTIVE via Phoenix Client
> ---------------------------------------------------------------
>
>                 Key: PHOENIX-5094
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5094
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.14.1
>            Reporter: Monani Mihir
>            Assignee: Kiran Kumar Maturi
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0
>
>         Attachments: PHOENIX-5094-4.14-HBase-1.3.01.patch, PHOENIX-5094-4.14-HBase-1.3.02.patch,
PHOENIX-5094-4.14-HBase-1.3.03.patch, PHOENIX-5094-4.14-HBase-1.3.04.patch, PHOENIX-5094-4.14-HBase-1.3.05.patch,
PHOENIX-5094-master.01.patch, PHOENIX-5094-master.02.patch, PHOENIX-5094-master.03.patch
>
>
> Suppose Index is in INACTIVE state and Client load is running continuously. With INACTIVE
State, client will keep maintaining index.
> Before Rebuilder could run and bring index back in sync with data table, If some mutation
for Index fails from client side, then client will transition Index state (From INACTIVE-->
PENDING_DISABLE).
> If client succeeds in writing mutation in subsequent retries, it will transition Index
state again ( From PENDING_DISABLE --> ACTIVE) .
> Above scenario will leave some part of Index out of sync with data table.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message