The Cassandra pod will get scheduled to run on a different worker node,
provided there is an available node that satisfies affinity rules, resource
requirements, etc. And you are correct that the volume will get remounted.
If however you are using a local or hostPath volume, then it will be lost
an
Thanks John for the answer.
Regards
Manish
On Tue, Jul 28, 2020 at 11:39 PM John Sanda wrote:
> The Cassandra pod will get scheduled to run on a different worker node,
> provided there is an available node that satisfies affinity rules, resource
> requirements, etc. And you are correct that the
Hi,
Logically, i do not need to use multiple DCs(cluster is not geographically
separated), but i wonder if splitting the cluster to two half (two separate dc)
would decrease overhead of node ack/communication and result in better (write)
performance?
Sent using https://www.zoho.com/mail/
PROBABLY not, unless you've got a very very clever idea of using local
consistency levels or somehow taking advantage of write forwarding in a way
I havent personally figured out yet (maybe if you had a very high replica
count per DC, then using forwarding and EACH_QUORUM may get fun, but you'd
be
Thanks for your immediate and clear response, Jeff
Sent using https://www.zoho.com/mail/
On Wed, 29 Jul 2020 08:00:33 +0430 Jeff Jirsa wrote
PROBABLY not, unless you've got a very very clever idea of using local
consistency levels or somehow taking advantage of write forwarding
