[
https://issues.apache.org/jira/browse/CASSANDRA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-13152:
--------------------------------------
Bug Category: Parent values: Availability(12983)Level 1 values: Process
Crash(12992)
Severity: Critical (was: Normal)
> UPDATE on counter columns with empty list as argument in IN disables cluster
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-13152
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13152
> Project: Cassandra
> Issue Type: Bug
> Environment: Linux Ubuntu 16
> 3 Virtual machines
> Reporter: jorge collinet
> Assignee: Benjamin Lerer
> Priority: Urgent
> Fix For: 3.0.11, 3.11.0, 4.0
>
>
> On a 3 node cluster
> with this table (replication factor of 2):
> {code}
> 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)
> );
> {code}
> If I execute
> {code}
> UPDATE user_items_rec_history
> SET counter = counter + 1
> WHERE reference_id = 1 AND country = '' AND portal = '' AND app_name = '' AND
> recommended_id IN ();
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
