phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Monani Mihir (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-5094) Index can transition from INACTIVE to ACTIVE via Phoenix Client
Date Thu, 10 Jan 2019 10:34:00 GMT
Monani Mihir created PHOENIX-5094:
-------------------------------------

             Summary: 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: 4.14.1, 5.0.0
            Reporter: Monani Mihir


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