[
https://issues.apache.org/jira/browse/CASSANDRA-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045670#comment-15045670
]
Paulo Motta commented on CASSANDRA-10474:
-----------------------------------------
CASSANDRA-10774 now fails stream session on any error, at least it does not
hang forever. Should we still not fail the session and print a warning if
secondary index rebuild fail?
I guess its simpler to just fail the stream session. In case we decide for
printing a warning instead, I think we would need to make that warning
persistent if the user does not run nodetool rebuild_index, otherwise it may
assume the secondary indexes are consistent, since the stream session was
successful (and the initial warning was missed).
> Streaming should tolerate secondary index build failure
> -------------------------------------------------------
>
> Key: CASSANDRA-10474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10474
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Reporter: Yuki Morishita
> Labels: streaming
> Fix For: 2.1.x, 2.2.x
>
>
> When streaming failed to build secondary index at the end of streaming (like
> in CASSANDRA-10449), streaming session can hang as it throws exception
> without catching it.
> Streaming should tolerate secondary index build failure, and instead of
> failing (hanging) streaming session, it should WARN user and go on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
