You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Monani Mihir (JIRA)" <ji...@apache.org> on 2019/01/10 10:36:00 UTC
[jira] [Commented] (PHOENIX-5094) Index can transition from
INACTIVE to ACTIVE via Phoenix Client
[ https://issues.apache.org/jira/browse/PHOENIX-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739284#comment-16739284 ]
Monani Mihir commented on PHOENIX-5094:
---------------------------------------
FYI [~vincentpoon] [~lhofhansl] [~tdsilva]
This scenario is just like PHOENIX-5080 .
> 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
> Priority: Major
>
> 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)