Re: Reg :- Multiple Node Cluster set up in Virtual Box

2017-11-07 Thread @Nandan@
Hi Users, I successfully configured 2 Nodes Cluster , but when I configured 3rd Node and try to join them , then 3rd node is not able to join Cluster and I am getting below message. Please correct me in case of I am wrong at some place. > WARN [GossipStage:1] 2017-11-07 17:01:42,706

RE: Reg :- Multiple Node Cluster set up in Virtual Box

2017-11-07 Thread Kyrylo Lebediev
Nandan, There are several options available how this can be done. For example, you may configure 2 network adapters per each VM: 1) NAT: in order the VM to have access to the Internet 2) Host-only Adapter - for internode communication setup (listen_address, rpc_address). Static IP configuration

Fwd: Stable Cassandra 3.x version for production

2017-11-07 Thread shini gupta
Hi Which version of Cassandra 3.x is stable and production-ready? Regards

Re: Stable Cassandra 3.x version for production

2017-11-07 Thread Carlos Rolo
DSE is already pushing 3.11 in 5.1 If you're going into 3.x either 3.11.1 or 3.0.15. I would recommend 3.11.1 to take advantage of a couple of features (ex: Slow query log) that you don't have on 3.0. If you're stable on 2.x and you don't need any new feature, you can leave it there safely

Re: Stable Cassandra 3.x version for production

2017-11-07 Thread Herbert Fischer
I know that people usually prefers to use the 3.0.x branch because that's the one that is underneath DSE. I've never heard of anyone using Cassandra > 3.0.x on production. On Tue, Nov 7, 2017 at 11:29 AM, shini gupta wrote: > > > Hi > > Which version of Cassandra 3.x

RE: Stable Cassandra 3.x version for production

2017-11-07 Thread Harika Vangapelli -T (hvangape - AKRAYA INC at Cisco)
We are using version 3.7 in prod. [http://wwwin.cisco.com/c/dam/cec/organizations/gmcc/services-tools/signaturetool/images/logo/logo_gradient.png] Harika Vangapelli Engineer - IT hvang...@cisco.com Tel: Cisco Systems, Inc. United States cisco.com

Re: Stable Cassandra 3.x version for production

2017-11-07 Thread Jeff Jirsa
3.0.15 is likely fine for production, but like any database, you should test it with your data in a test environment prior to deploying to prod. I haven't personally used 3.11.1, though the important parts are likely very similar to 3.0.15. On Tue, Nov 7, 2017 at 5:35 AM, Herbert Fischer <

RE: Stable Cassandra 3.x version for production

2017-11-07 Thread Steinmaurer, Thomas
Latest DSE is based on 3.11 (possibly due to CASSANDRA-12269, but just a guess). For us (only), none of 3.0+/3.11+ qualifies for production to be honest, when you are familiar with having 2.1 in production. · 3.0 needs more hardware resources to handle the same load =>

Re: 3.0.6 - CorruptSSTableException

2017-11-07 Thread Riccardo Ferrari
Thanks you Adama, Even though it refers to an older C* version it is still a good starting point, thanks! I ended up restoring the table from a previous snapshot. The server booted up ok and joined the ring. Hopefully the repair process will take care of synching back the node. Best, On Tue,

Re: Stable Cassandra 3.x version for production

2017-11-07 Thread Jon Haddad
I regularly work with teams that have 3.11.{0.1} in prod, and would recommend it for new clusters. Avoid materialized views and SASI until you really understand how they work and their limitations. MVs solve about one use case correctly, SASI is good if you’re querying a single partition

RE: 3.0.6 - CorruptSSTableException

2017-11-07 Thread adama.diabate
Hi Riccardo, The following may help me, as the case described there is similar to yours ! https://engineering.gosquared.com/dealing-corrupt-sstable-cassandra Regards. De : Riccardo Ferrari [mailto:ferra...@gmail.com] Envoyé : lundi 6 novembre 2017 16:16 À : user@cassandra.apache.org Objet :

RE: system_auth permissions issue C* 2.0.14

2017-11-07 Thread Chandan Goel
Hi Avinash, Please see if you have given permissions to the user (logged in) on the table and all related Materialized Views. Thanks Chandan From: pabbireddy avinash [mailto:pabbireddyavin...@gmail.com] Sent: Friday, November 03, 2017 3:06 PM To: user@cassandra.apache.org Subject: system_auth

RE: Cassandra using a ton of native memory

2017-11-07 Thread Austin Sharp
Follow-up for anyone interested: disabling the Windows page file (which Windows makes kind of a pain) appears to resolve all issues. Cassandra is still using lots of memory but it gives it up as appropriate. From: DuyHai Doan [mailto:doanduy...@gmail.com] Sent: Friday, November 3, 2017 11:25