Thanks All !!
I think the intent of the JIRA https://issues.apache.org/
jira/browse/CASSANDRA-6961 was to primarily deal with stale information after
outages and give opportunity for repairing the data before a node joins the
cluster. If a node started with join_ring=false doesn't accept writes
Beware the Java Driver limitations around whitelisting IPs.
Works fine in Python.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
Pythian - Love your data
rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
There is a talk from cassandra summit 2016 about coordinator nodes by Eric
Lubow from SimpleReach. He explains how you can use that join_ring=false.
On Tue, Dec 20, 2016 at 10:23 PM, kurt Greaves wrote:
> It seems that you're correct in saying that writes don't propagate
It seems that you're correct in saying that writes don't propagate to a
node that has join_ring set to false, so I'd say this is a flaw. In reality
I can't see many actual use cases in regards to node outages with the
current implementation. The main usage I'd think would be to have
additional
No responses yet :)
Any C* expert who could help on join_ring use case and the concern raised?
Thanks
Anuj
On Tue, 13 Dec, 2016 at 11:31 PM, Anuj Wadehra wrote:
Hi,
I need to understand the use case of join_ring=false in case of node outages.
As per
Can anyone help me with join_ring and address my concerns?
Thanks
Anuj
On Tue, 13 Dec, 2016 at 11:31 PM, Anuj Wadehra wrote:
Hi,
I need to understand the use case of join_ring=false in case of node outages.
As per
Hi,
I need to understand the use case of join_ring=false in case of node outages.
As per https://issues.apache.org/jira/browse/CASSANDRA-6961, you would want
join_ring=false when you have to repair a node before bringing a node back
after some considerable outage. The problem I see with