phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Kumar Maturi (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-5094) Index can transition from INACTIVE to ACTIVE via Phoenix Client
Date Tue, 29 Jan 2019 16:33:00 GMT


Kiran Kumar Maturi updated PHOENIX-5094:
    Attachment: PHOENIX-5094-4.14-HBase-1.3.03.patch

> Index can transition from INACTIVE to ACTIVE via Phoenix Client
> ---------------------------------------------------------------
>                 Key: PHOENIX-5094
>                 URL:
>             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-4.14-HBase-1.3.03.patch, PHOENIX-5094-4.14-HBase-1.3.03.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-->
> 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

View raw message