r haul in the way hints have been implemented.
>>
>> Recommend reading up this blog article:
>>
>> http://www.datastax.com/dev/blog/whats-coming-to-cassandra-in-3-0-improved-hint-storage-and-delivery
>>
>> hope this helps
>> Jan/
>>
>>
>>
le:
>
> http://www.datastax.com/dev/blog/whats-coming-to-cassandra-in-3-0-improved-hint-storage-and-delivery
>
> hope this helps
> Jan/
>
>
> --------
> On Thu, 4/21/16, Jens Rantil wrote:
>
> Subject: Re: When are hints writt
Hi Jens,
I suspected that write_request_timeout_in_ms was involved, so I have
already raised that to 12 on all nodes in the cluster, and to 13 on
the client. This is much longer that any of our writes takes.
I looked at the hints files that where being written, and they where all 42
bytes
been implemented.
Recommend reading up this blog article:
http://www.datastax.com/dev/blog/whats-coming-to-cassandra-in-3-0-improved-hint-storage-and-delivery
hope this helps
Jan/
On Thu, 4/21/16, Jens Rantil wrote:
Subject: Re: When are hints
Hi again Bo,
I assume this is the piece of documentation you are referring to?
http://docs.datastax.com/en/cassandra/2.0/cassandra/dml/dml_about_hh_c.html?scroll=concept_ds_ifg_jqx_zj__performance
> If a replica node is overloaded or unavailable, and the failure detector
has not yet marked it dow
Hi Jens,
Thank you for the tip!
ALL would definitely cure our hints issue, but as you note, it is not
optimal as we are unable to take down nodes without clients failing.
I am most probably overlooking something in the documentation, but I cannot
see any description of when hints are written othe
how do you unsubscribe
From: Bo Finnerup Madsen
Sent: Wednesday, April 20, 2016 9:38 AM
To: user@cassandra.apache.org
Subject: When are hints written?
Hi,
We have a small 5 node cluster of m4.xlarge clients that receives writes from
~20 clients. The clients
Also, 3.0.3 is a very new Cassandra version. IMHO, you might want to
consider not using bleeding edge in production. See
https://www.eventbrite.com/engineering/what-version-of-cassandra-should-i-run/
and http://stackoverflow.com/q/25155916.
Cheers,
Jens
On Wed, Apr 20, 2016 at 3:39 PM Bo Finneru
Hi Bo,
> In our case, I would like for the cluster to wait for the write to be
persisted on the relevant nodes before returning an ok to the client. But I
don't know which knobs to turn to accomplish this? or if it is even
possible :)
This is what write consistency option is for. Have a look at
h
Hi,
We have a small 5 node cluster of m4.xlarge clients that receives writes
from ~20 clients. The clients will write as fast as they can, and the whole
process is limited by the write performance of the cassandra cluster.
After we have tweaked our schema to avoid large partitions, the load is
goi
10 matches
Mail list logo