unsubscribe
De : Shravan R [mailto:skr...@gmail.com]
Envoyé : mardi 16 avril 2019 17:04
À : user@cassandra.apache.org
Objet : Re: multiple snitches in the same cluster
Thanks Paul
On Tue, Apr 16, 2019 at 9:52 AM Paul Chandler
mailto:p...@redshots.com>> wrote:
Hi Shravan,
We did not s
Thanks Paul
On Tue, Apr 16, 2019 at 9:52 AM Paul Chandler wrote:
> Hi Shravan,
>
> We did not see any down sides of using the GossipingPropertyFileSnitch, in
> fact being able to handcraft the DC allowed us to easily create “virtual”
> cassandra datacenters within the google DC, something we hav
Hi Shravan,
We did not see any down sides of using the GossipingPropertyFileSnitch, in fact
being able to handcraft the DC allowed us to easily create “virtual” cassandra
datacenters within the google DC, something we have used for splitting multi
tenanted clusters. I am not sure how easy that
Thanks Paul. Glad to know that you are speaking on the very subject soon.
Even though you are on GCP, you are still tied with
GossipingPropertyFileSnitch and not enjoying the GoogleCloudSnitch. If it
is not too much to ask, other than hand stitching RACK and DC in
cassandra-rackdc.properties are
Sravan,
When we migrated to google we just continued using the
GossipingPropertyFileSnitch, we did not try and use the google version of the
snitch.
The only downside is the need to manually setup the cassandra-rackdc.properties
file, but for us that was controlled by puppet anyway, so it was
Can we have multiple snitches within the same cluster?
Reason for the ask: I need to find an optimal migration path from on prem
DC to AWS.
Currently the cluster has TWO on prem DCs and the end cluster state should
be TWO DCs in same region/multiple zones in AWS.
I know there is EC2Snitch - but t
