flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4123) CassandraWriteAheadSink can hang on cassandra failure
Date Tue, 12 Jul 2016 12:48:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372825#comment-15372825
] 

ASF GitHub Bot commented on FLINK-4123:
---------------------------------------

Github user tillrohrmann commented on the issue:

    https://github.com/apache/flink/pull/2183
  
    Changes look good to me. Thanks for your contribution @zentol. Will be merging this PR.


> 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)

Mime
View raw message