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

Shenghua Wan commented on CASSANDRA-10347:
------------------------------------------

First thank you for looking into this issue.

[~pauloricardomg] To you question, I have not tried 
mapreduce.output.bulkoutputformat.maxfailedhosts property. I have read the 
source code and thought this property only gave up when certain number of host 
connections failed. However, I still want the streaming continue if there exist 
some hosts alive, even exceeding the threshold. Therefore, to solve the problem 
of my use case (skip connecting to lost hosts), I have implemented something 
just like "mapreduce.output.bulkoutputformat.ignorehosts" property, e.g.


> Bulk Loader API could not tolerate even node failure
> ----------------------------------------------------
>
>                 Key: CASSANDRA-10347
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10347
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Shenghua Wan
>            Assignee: Paulo Motta
>             Fix For: 2.1.x, 2.2.x, 3.0.x
>
>
> When user uses CqlBulkOutputFormat, it tries to stream to all the nodes in 
> the token range, which includes the dead nodes. Therefore, the stream failed. 
> There was a design in C* API to allow stream() method to have a list of 
> ignore hosts, but it was not utilized.
> The empty-argument stream() method is called in all existing versions of C*, 
> i.e.
> in v2.0.11, 
> https://github.com/apache/cassandra/blob/cassandra-2.0.11/src/java/org/apache/cassandra/hadoop/AbstractBulkRecordWriter.java#L122
> in v2.1.5, 
> https://github.com/apache/cassandra/blob/cassandra-2.1.5/src/java/org/apache/cassandra/hadoop/AbstractBulkRecordWriter.java#L122
> and current trunk branch 
> https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/hadoop/cql3/CqlBulkRecordWriter.java#L241



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

Reply via email to