On Tue, Aug 5, 2014 at 11:53 AM, Clint Kelly wrote:
> Ah FWIW I was able to reproduce the problem by reducing
> "range_request_timeout_in_ms." This is great since I want to increase
> the timeout for batch jobs where we scan a large set of rows, but
> leave the timeout for single-row queries alo
Ah FWIW I was able to reproduce the problem by reducing
"range_request_timeout_in_ms." This is great since I want to increase
the timeout for batch jobs where we scan a large set of rows, but
leave the timeout for single-row queries alone.
Best regards,
Clint
On Tue, Aug 5, 2014 at 11:42 AM, Cl
Hi Rob,
Thanks for your feedback. I understand that use of ALLOW FILTERING is
not a best practice. In this case, however, I am building a tool on
top of Cassandra that allows users to sometimes do things that are
less than optimal. When they try to do expensive queries like this,
I'd rather pro
How much did you reduce *read_request_timeout_in_ms* on your local machine?
Cassandra timeout during read query is higher than one machine because
Cassandra server must run the read operation in more servers (so you have
network traffic).
2014-08-05 14:54 GMT-03:00 Robert Coli :
> On Tue, Aug 5,
On Tue, Aug 5, 2014 at 10:01 AM, Clint Kelly wrote:
> Allow me to rephrase a question I asked last week. I am performing some
> queries with ALLOW FILTERING and getting consistent read timeouts like the
> following:
>
ALLOW FILTERING should be renamed PROBABLY TIMEOUT in order to properly
descr
Hi all,
Allow me to rephrase a question I asked last week. I am performing some
queries with ALLOW FILTERING and getting consistent read timeouts like the
following:
com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra
timeout during read query at consistency ONE (1 responses we
