Details
-
Bug
-
Status: Resolved
-
Urgent
-
Resolution: Fixed
-
None
-
Linux Ubuntu 16
3 Virtual machines
-
Availability - Process Crash
-
Critical
Description
On a 3 node cluster
with this table (replication factor of 2):
CREATE TABLE tracking.item_items_rec_history ( reference_id bigint, country text, portal text, app_name text, recommended_id bigint, counter counter, PRIMARY KEY (reference_id, country, portal, app_name, recommended_id) );
If I execute
UPDATE user_items_rec_history SET counter = counter + 1 WHERE reference_id = 1 AND country = '' AND portal = '' AND app_name = '' AND recommended_id IN ();
Take note that the IN is empty
The cluster starts to malfunction and responds a lot of timeouts to any query.
After resetting some of the nodes, the cluster starts to function normally again.