cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10347) Bulk Loader API could not tolerate even node failure
Date Mon, 28 Sep 2015 19:09:04 GMT


Paulo Motta commented on CASSANDRA-10347:

bq. Isn't using mapreduce.output.bulkoutputformat.maxfailedhosts a better way to do this?
Does that not work for this use case?

Probably yes, but [~wanshenghua] could tell better, did you try the {{mapreduce.output.bulkoutputformat.maxfailedhosts}}

Unfortunately I just discovered that property after implementing the new one, my bad. Anyway,
I guess the parameters are not mutually exclusive, as you may want still want to blacklist
nodes that are alive. Since it's already implemented and to be consistent with sstable loader,
I think it's still valid to have an {{ignorehosts}} property in addition to {{maxfailedhosts}}.

> Bulk Loader API could not tolerate even node failure
> ----------------------------------------------------
>                 Key: CASSANDRA-10347
>                 URL:
>             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,
> in v2.1.5,
> and current trunk branch

This message was sent by Atlassian JIRA

View raw message