You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2016/07/12 16:09:20 UTC

[jira] [Resolved] (FLINK-4123) CassandraWriteAheadSink can hang on cassandra failure

     [ https://issues.apache.org/jira/browse/FLINK-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann resolved FLINK-4123.
----------------------------------
    Resolution: Fixed

Fixed via 5c2da21f25741502dd8ca64ce9d314a1ebea1441

> CassandraWriteAheadSink can hang on cassandra failure
> -----------------------------------------------------
>
>                 Key: FLINK-4123
>                 URL: https://issues.apache.org/jira/browse/FLINK-4123
>             Project: Flink
>          Issue Type: Bug
>          Components: Streaming Connectors
>    Affects Versions: 1.1.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Blocker
>             Fix For: 1.1.0
>
>
> The CassandraWriteAheadSink verifies that all writes send to cassandra have been applied by counting how many were sent and how many callbacks were activated. Once all writes were sent the sink enters into a loop that is only exited once both counts are equal.
> Thus, should cassandra crash after all writes were sent, without having acknowledged all writes, the sink will deadlock in the loop.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)