drivers in other languages.
Thanks
Alok Dwivedi
Senior Consultant
https://www.instaclustr.com/
On Fri, 26 Jul 2019 at 20:03, Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:
> Thanks Sean,
>
> In my use case all my clusters are multi DC, and I am trying my best
> eff
Hi Bharat
As already pointed out below, there are some limitations and issues with
Materialized views (depending upon your version). This blog post also
summarizes some issues/caveats with MV
https://www.instaclustr.com/apache-cassandra-materialized-view-instaclustr-support/
Thanks
Alok Dwivedi
chose during streaming
didn’t had it) I sync that with repair. Then I would move on to doing same
steps with next dead node to be replaced.
Thanks
Alok Dwivedi
Senior Consultant
https://www.instaclustr.com/platform/
From: Fd Habash
Reply-To: "user@cassandra.apache.org"
Date: Thursda
dead node the new token range selection does not applies as
the replacing node just owns the token ranges of the dead node. I think that’s
why the restriction of only replacing one node at a time does not applies in
this case.
Thanks
Alok Dwivedi
Senior Consultant
https://www.instaclustr.com
/documentation/cluster-management/managing-tombstones/
<https://www.instaclustr.com/support/documentation/cluster-management/managing-tombstones/>
Alok Dwivedi
Senior Consultant
https://www.instaclustr.com/
> On 24 Apr 2019, at 20:20, onmstester onmstester
> wrote:
>
> Found th
Could it be related to hinted hand offs being stored in Node1 and then
attempted to be replayed in Node2 when it comes back causing more load as new
mutations are also being applied from cassandra-stress at same time?
Alok Dwivedi
Senior Consultant
https://www.instaclustr.com/
> On 26
hould be fine. Some related tickets for reference.
https://datastax-oss.atlassian.net/browse/JAVA-264
<https://datastax-oss.atlassian.net/browse/JAVA-264>
https://datastax-oss.atlassian.net/browse/JAVA-313
<https://datastax-oss.atlassian.net/browse/JAVA-313>
Thanks
Alok Dwivedi
Senior Co
Your delete query
>> "DELETE FROM myTable WHERE course_id = 'C' AND assignment_id = 'A1';”.
will generate multi row range tombstones. Since you are reading entire
partition which effectively will be read in pages (slice query equivalent) you
may get tombstones in certain pages depending upon how