[PHOENIX-4980] Mismatch in row counts between data and index tables while multiple clients try to upsert data

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 4.14.0
• Fix Version/s: 4.14.1
• Labels: LocalIndex globalMutableSecondaryIndex secondaryIndex
• Assignee: Vincent Poon
• Reporter: Abhishek Talluri
• Created: 17/Oct/18 17:10
• Updated: 22/Oct/18 19:56
• Resolved: 22/Oct/18 18:46

Description

Phoenix table has A,B,C,D,E as its columns and A as the primary key for the table.

CREATE TABLE TEST (A VARCHAR NOT NULL PRIMARY KEY, B VARCHAR, C VARCHAR, D VARCHAR , E VARCHAR);

Global index is built on D & E
CREATE INDEX TEST_IND on TEST (D,E);

Client 1 updates A,B,C whereas client 2 updates A,B,D,E

I used phoenix 5.14.2-1.cdh5.14.2.p0.3 parcel to test this issue. Ran with two threads that load data using upserts reading from the csv file. Within 10 iterations, i could observe the difference in the row counts between data table and index table. Attaching the code used to test this behavior. This issue also exists in both Global and Local indexes.

Issue Links

• is related to: PHOENIX-4089 Prevent index from getting out of sync with data table under high concurrency
• is related to: PHOENIX-4988 Incorrect index rowkey generated when updating only non-indexed columns after a delete