You just need to send mail to user@cassandra.apache.org ..Everyone on mailing
list including you will get the mail..
Anuj
Sent from Yahoo Mail on Android
From:"xutom"
Date:Wed, 9 Dec, 2015 at 7:28 am
Subject:Re:Re: Re: Re: Cassandra Tuning Issue
Hi Anuj,
Thanks! I will retry now!
ing your memory, it will be used for OS caching and
> you can get even better performance..
>
> Thanks
> Anuj
>
> Sent from Yahoo Mail on Android
> <https://overview.mail.yahoo.com/mobile/?.src=Android>
> ------
> *From*:"Jack Krupansky"
y about wasting your memory, it will be used for OS caching and you
can get even better performance..
Thanks
Anuj
Sent from Yahoo Mail on Android
|
From:"Jack Krupansky"
Date:Tue, 8 Dec, 2015 at 8:07 pm
Subject:Re: Re: Re: Cassandra Tuning Issue
Great! Make sure to inform the C* ema
/cassandra/install/installRecommendSettings.html
Dont worry about wasting your memory, it will be used for OS caching and you
can get even better performance..
Thanks
Anuj
Sent from Yahoo Mail on Android
From:"Jack Krupansky"
Date:Tue, 8 Dec, 2015 at 8:07 pm
Subject:Re: Re: Re: Cassan
Great! Make sure to inform the C* email list as well so that others know.
-- Jack Krupansky
On Tue, Dec 8, 2015 at 7:44 AM, xutom wrote:
>
>
> Dear Jack,
> Thank you very much! Now we have much better performance when we
> insert the same partition keys in the same batch.
>
> jerry
>
> At 2
Dear Jack,
Thank you very much! Now we have much better performance when we insert the
same partition keys in the same batch.
jerry
At 2015-12-07 13:08:31, "Jack Krupansky" wrote:
If you combine inserts for multiple partition keys in the same batch you negate
most of the effect of tok
If you combine inserts for multiple partition keys in the same batch you
negate most of the effect of token-aware routing. It's best to insert only
rows with the same partition key in a single batch. You also need to set
the partition key for routing for the batch.
Also, RF=2 is not recommended si
What version of C* are you using; what JVM version - you showed a partial GC
config but if that is still CMS (not G1) then you are going to have insane GC
pauses...
Depending on C* versions are you using on/off heap memtables and what type
Those are the sorts of issues related to fat nodes; I'
What replication factor are you using? Even if your writes use CL.ONE,
Cassandra will be attempting writes to the replica nodes in the background.
Are your writes "token aware"? If not, the receiving node has the overhead
of forwarding the request to the node that owns the token for the primary
ke
