Re: Cassandra did not start listening for CQL clients

Open a jira for it and lets change it? -- Jeff Jirsa > On Jun 29, 2017, at 8:04 AM, Mike Adamson wrote: > > I've honestly no idea but it is still defaulting to false in Config.java. > I'm assuming it will change to defaulting to true when thrift is finally > removed.

Re: Cassandra did not start listening for CQL clients

I've honestly no idea but it is still defaulting to false in Config.java. I'm assuming it will change to defaulting to true when thrift is finally removed. On Thu, 29 Jun 2017 at 15:34 Tomas Repik wrote: > Thanks Mike, > > now I remember this option, but I thought it was set

Re: Cassandra did not start listening for CQL clients

Thanks Mike, now I remember this option, but I thought it was set to true by default. Any reasons why false is the default? - Original Message - > Hi Tomas, > > Try adding: > > start_native_transport: true > > to your config. > > Cheers, > MikeA >

Re: Cassandra did not start listening for CQL clients

Hi Tomas, Try adding: start_native_transport: true to your config. Cheers, MikeA On Thu, 29 Jun 2017 at 15:08 Tomas Repik wrote: > Hello, > > I've tried to create a minimal config file that is needed to start > Cassandra server. Is it even possible? > What is the minimal

Cassandra did not start listening for CQL clients

Hello, I've tried to create a minimal config file that is needed to start Cassandra server. Is it even possible? What is the minimal set of options that need to be set in the cassandra.yaml file in order for Cassandra to run flawlessly. These are the options I use: commitlog_sync: periodic

Review request: CASSANDRA-13547

Hi, while using debian packages, we noticed that HeapDumpPath set in /etc/casandra/cassandra-env.sh or jv.options was not respected. This was due to the fact that debian init script was overriding it by calling /usr/sbin/cassandra with its own settings. A jira have been opened with attached