Re: Cassandra MV insert Warning

It is a bug that may happen on MV lock contention and fixed by https://issues.apache.org/jira/browse/CASSANDRA-12689 2016-12-15 7:58 GMT+01:00 안정아 : > Hi, All. > > > > *Issue on MaterializedViews Inserting > > > > environment) 6-cassandra servers 1cluster Version 3.7 JAVA

Cassandra MV insert Warning

Hi, All.   *Issue on MaterializedViews Inserting   environment) 6-cassandra servers 1cluster Version 3.7 JAVA version 1.8 cassandra java driver 3.1.0 data modiling ) column name : ex] A, B, C BaseTable((A, B), C), MV1((A, B), D, E), MV2((A, B), F, G), MV3((A, B), H, I)   details

Re: Join_ring=false Use Cases

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

Re: Configure NTP for Cassandra

Thanks Martin. Agree, setting up our own internal servers will help save some firewall traffic, simplify security management and reduce load on public servers which is an ethical thing to do. As the blog recommended setting up own internal servers for Cassandra, I wanted to make sure that there

Re: Cassandra Different cluster gossiping to each other

This is possible if some of the nodes are available in system peer table of the other cluster.this usually occurs when we decommission nodes from one cluster and add to another cluster.also make sure that before adding a node newly to a cluster all data in drives are properly wiped out . Sent

Re: Cassandra Different cluster gossiping to each other

You have somehow mixed seeds (or re-used IP addresses). The good news is that different cluster names have prevented you from pretty ugly data issues. Check your seed lists and system.peers on your hosts for IPs belonging to the wrong cluster, and remove them. From: Abhishek Kumar

Cassandra Different cluster gossiping to each other

Hi All, I am getting below log in my system.log GossipDigestSynVerbHandler.java:52 - ClusterName mismatch from /192.XXX.AA.133 QA Columbia Cluster! = QA Columbia Cluster new 192.XXX.AA.133 Cluster name is QA Columbia Cluster And on which server I am getting this error cluster name is: QA