[
https://issues.apache.org/jira/browse/CASSANDRA-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977061#comment-14977061
]
Ariel Weisberg commented on CASSANDRA-10474:
--------------------------------------------
[Looks like this works on
trunk?|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/streaming/StreamReceiveTask.java#L179]
I see exception handling for cfs.indexManager.buildAllIndexesBlocking(readers).
Is that enough or is there additional cleanup necessary if that throws. I know
we added a lot of stuff in 3.0 to handle failure during streaming.
> Streaming should tolerate secondary index build failure
> -------------------------------------------------------
>
> Key: CASSANDRA-10474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10474
> Project: Cassandra
> Issue Type: Bug
> Reporter: Yuki Morishita
> Labels: streaming
> Fix For: 2.1.x, 2.2.x, 3.1
>
>
> 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)
