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 loc
Yes, you have to run a nodetool removenode to decomission completely.. this
will also allow another node with the same ip different HashId to join the
cluster..
Thanks
-suraj
On Tue, May 16, 2017 at 9:01 AM Mark Furlong wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> I have a node I decommissioned on a
Hello,
I am tying to find a way to PREVENT just one of my keyspaces to not sync to
the other datacenter.
I have 2 datacenters setup this way :
Datacenter: DC:4.4.4.4
==
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effecti
nserts shouldn’t populate,
> ideally.
>
> On May 16, 2017, at 3:19 PM, suraj pasuparthy
> wrote:
>
> elp me fig
>
>
>
--
Suraj Pasuparthy
cisco systems
Software Engineer
San Jose CA
s keyspace from
replicating :(.. not sure why this does not work
Thanks
Suraj
On Tue, May 16, 2017 at 3:06 PM Nitan Kainth wrote:
> check for datafiles on filesystem in both DCs.
>
> On May 16, 2017, at 4:42 PM, suraj pasuparthy
> wrote:
>
> So i though the same,
> I see
cassandra ensure that first Record
A is synced to Table A in Datacenter 2 and then the Record B syncs to table
B ?
Is there a possibility of "out of order " syncs between datacenters ?
--
Suraj Pasuparthy
;
>
> Thanks
> Pranay.
>
> On Thu, Jul 6, 2017 at 2:01 AM, suraj pasuparthy <
> suraj.pasupar...@gmail.com> wrote:
>
>> Hello Experts,
>> I had a question
>>
>> We have a multi DC cluster for cassandra and wanted to confirm one
>> behavi
or a single DC (region).
>> Currently I am using GossipingPropertyFileSnitch.
>>
>> I look forward for your input.
>>
>
> --
Suraj Pasuparthy
