Is this Java 8 with the G1 garbage collector or CMS? With Java 7 and CMS,
garbage collection can cause delays like you are seeing. I haven’t seen that
problem with G1, but garbage collection is where I would start looking.
Sean Durity
From: Ted Pearson [mailto:t...@tedpearson.com]
Sent:
Hello
We have a usecase where we need to support triggers with multiple
datacenters.
The use case is we need is
1) Data is written into DC1.
2) The Sync configured will sync the data to DC2
3) when the data is written into DC2, we need a trigger to fire on DC2.
I have tested the triggers for a
Trigger only gets executed on the coordinator. There's no remote DC
trigger.
What you need is Change Data Capture (CDC).
https://issues.apache.org/jira/browse/CASSANDRA-8844
On Tue, Jan 17, 2017 at 9:40 AM suraj pasuparthy
wrote:
> Hello
> We have a usecase where
Thanks for the feedback everyone! Redis `zincryby` and `zrangebyscore` is
indeed what we use today.
Caching the resulting 'sorted sets' in redis is exactly what I plan to do.
There will be tens of thousands of these sorted sets, each generally with <10k
items (with maybe a few exceptions going
On 01/17/2017 05:43 AM, Artem Rokhin wrote:
> Do you have any estimates for Cassandra 4.0 release?
Follow the dev@ mailing list for info on upcoming release votes and
other release discussion.
http://mail-archives.apache.org/mod_mbox/cassandra-dev/
--
Kind regards,
Michael
On Tue, Jan 17, 2017 at 11:47 AM, Mike Torra wrote:
> Thanks for the feedback everyone! Redis `zincryby` and `zrangebyscore` is
> indeed what we use today.
>
> Caching the resulting 'sorted sets' in redis is exactly what I plan to do.
> There will be tens of thousands of
You could store the key -> score pairs in Cassandra, pull out the full
partition and repopulate the cache in redis with the top N whatever you
need. I'd only read the Cassandra values directly in order to repopulate
the cache.
I wouldn't try to score the score -> key values, the perf will be a
Hey Guan,
If it's the case that you actually replaced the nodes and already assigned
new IP's to them this is probably common behaviour. Since Cassandra has a
retention policy to keep dead nodes for 72 hours.
Best,
Malte
2017-01-17 0:29 GMT+01:00 Sun, Guan :
> Hi all,
>
>
Hey Guys!
Couldn’t find this information, so asking it here -
Do you have any estimates for Cassandra 4.0 release?
Thank you in advance.
==
Best Regards,
Artem Rokhin
JetBrains