Re: How does the "batch" commit log sync works

Hello Benedict and Edward, Thank you very much for the comments. I think the batch parameter is useful when doing some transactional processing on C* where we need atomicity and higher durability. Anyways, I think it is not working as expected at least in the latest versions in 2.1 and 2.2. So,

Re: Securing a Cassandra 2.2.6 Cluster

I'm not sure why you aren't able to connect with cqlsh, there may be something in your log files to help figure that out. As for your config, even if you do figure out why you can't connect, you're still going to have to change your settings since you won't be able to connect to your cluster from

Re: Securing a Cassandra 2.2.6 Cluster

Hi guys, Thank you for your responses. Let me try to address them: - I just tried cqlsh directly with the IP, no change in behaviour. (I previously tried the hostnames, didn't work either.) - As for the "empty" ..._address: I meant that I leave these blank. Please let me quote from

Re: Securing a Cassandra 2.2.6 Cluster

I always prefer to set the listen interface instead of listen adress Both nodes can be seeds. In fact, there should be more than one seed. Having your first 2 nodes as seeds is usual the correct thing to do. On Sun, Oct 30, 2016 at 8:28 AM Vladimir Yudovin wrote: > >Empty

Re: Securing a Cassandra 2.2.6 Cluster

Empty listen_address and rpc_address. What do you mean by "Empty"? You should set either ***_address or ***_interface. Otherwise Cassandra will not listen on port 9042. Open ports 9042, 7000 and 7001 for external communication. Only port 9042 should be open to the world, Port 7000 for

Re: Securing a Cassandra 2.2.6 Cluster

Dis you try the external IP with cqlsh? On Sun, Oct 30, 2016 at 8:12 AM Raimund Klein wrote: > Hi everyone, > > We've managed to set up a Cassandra 2.2.6 cluster of two physical nodes > (nodetool sees both of them, so I'm quite certain the cluster is indeed > active). My

Securing a Cassandra 2.2.6 Cluster

Hi everyone, We've managed to set up a Cassandra 2.2.6 cluster of two physical nodes (nodetool sees both of them, so I'm quite certain the cluster is indeed active). My steps to create the cluster were (this applies to both machines): - Empty listen_address and rpc_address. - Define a

Re: Cassandra failure during read query at consistency QUORUM (2 responses were required but only 0 replica responded, 2 failed)

Why does it prevent quorum? How to fix it? > On 28 Oct 2016, at 16:02, Edward Capriolo wrote: > > This looks like another case of an assert bubbling through try catch that > don't catch assert > > On Fri, Oct 28, 2016 at 6:30 AM, Denis Mikhaylov

Re: Two DCs assandra on Azure connection problem.

Hi Cliff,great, it helps, thank you! So it's still strange for me why - as I mentioned "I suspected connectivity problem, but tcpdump shows constant traffic on port 7001 between nodes.", and even in unresponsive state there was packet exchange. Also I don't see in Cassandra code enabling