[PHOENIX-5094] Index can transition from INACTIVE to ACTIVE via Phoenix Client

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Resolved
• Affects Version/s: 5.0.0, 4.14.1
• Fix Version/s: 4.15.0, 5.1.0, 4.14.2, 5.0.1
• Assignee: Kiran Kumar Maturi
• Reporter: Mihir Monani
• Created: 10/Jan/19 10:33
• Updated: 30/May/19 18:41
• Resolved: 01/Feb/19 19:29

Description

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.

Issue Links

• relates to: PHOENIX-5218 When INDEX_FAILURE_HANDLING_REBUILD_PERIOD is set, Phoenix Client can still transition Index from INACTIVE to ACTIVE