You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Dinesh Joshi (JIRA)" <ji...@apache.org> on 2019/01/15 06:53:00 UTC
[jira] [Commented] (CASSANDRA-14981) Cassandra fires
NoHostAvailable exception, but trigger receives update
[ https://issues.apache.org/jira/browse/CASSANDRA-14981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742802#comment-16742802 ]
Dinesh Joshi commented on CASSANDRA-14981:
------------------------------------------
Hi [~timurtibeyev], thanks for reporting this issue. Could you please post your cassandra config and steps that you took to create the cassandra cluster? Which Docker image are you using?
> Cassandra fires NoHostAvailable exception, but trigger receives update
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-14981
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14981
> Project: Cassandra
> Issue Type: Bug
> Environment: cassandra 3.11.3
> Reporter: Timur Tibeyev
> Priority: Major
> Attachments: Cassandra.png, Kafka consumer.png
>
>
> Cluster
> I have cluster with three nodes, cluster is created via `docker-compose`.
> All nodes in the cluster have `UN` (up normal) status, checked with `nodetool status`.
>
> Trigger
> Trigger receives event and produces `Kafka` record.
> All three nodes have same trigger.
>
> Table
> Here is my CQL query, `users` table replication factor is 2
> Consistency level is one
> ```
> CREATE KEYSPACE mytestdb WITH replication = \{ 'class':'SimpleStrategy', 'replication_factor':2 };
> USE mytestdb;
> CREATE TABLE IF NOT EXISTS users (
> id uuid,
> username text,
> phone text,
> lastname text,
> firstname text,
> PRIMARY KEY (id)
> );
> CREATE TRIGGER kafka_trigger ON users USING 'org.company.CassandraTrigger';
> ```
>
> Problem
> Everything worked fine so I wanted to check edge cases, I intentionally shut down 2 nodes, to check how `Cassandra` and trigger will perform.
> I started to make queries to single working node.
> Some inserts were processed correctly, but for some of them `NoHostAvailable` exception occurred, but trigger received this "failed" insert event and produced normal `Kafka` record
> The problem is - data was not saved to `Cassandra`, but trigger received update.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org