[
https://issues.apache.org/jira/browse/PHOENIX-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754126#comment-16754126
]
Kiran Kumar Maturi commented on PHOENIX-5094:
---------------------------------------------
[~vincentpoon] I have made some more changes for the patch. to identify the
1) increment made during the DISABLED to INACTIVE state transition by the
rebuilder
2) avoid resetting the counter when index transitions happens from INACTIVE to
PENDING_DISABLED.
can you please review and let me know if any further changes are needed.
> 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
> Attachments: PHOENIX-5094-4.14-HBase-1.3.01.patch,
> PHOENIX-5094-4.14-HBase-1.3.02.patch, PHOENIX-5094-master.01.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)
