Re: Cassandra loglevel in 3.11.x version

2019-09-06 Thread Jai Bheemsen Rao Dhanwada
Also, when I tried to play around with logback.xml to enable and disable debug logging, I noticed this behavior INFO logs are written both to debug.log and system.log If I comment out the ASYNCDEBUGLOG , no debug logs are generated. Is there way to log the INFO logs only in system.log and log DE

Re: Cassandra loglevel in 3.11.x version

2019-09-06 Thread Jai Bheemsen Rao Dhanwada
does anyone know if there is a documentation that lists all the classes for logs? On Fri, Sep 6, 2019 at 9:28 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thanks Allen, > > This works, is there any documentation that explain about all the > available logging levels? > > On Fri,

Re: Cassandra JVM configuration

2019-09-06 Thread John Sumsion
Pat, You might find this post useful in tuning G1 for Cassandra: * http://deliberate-thinking.blogspot.com/2019/05/tuning-g1-gc-for-cassandra.html This assumes a machine with 60-120G of RAM -- and your use case may be different than the clusters I've tuned, so take each step with care. Al

Re: Cassandra loglevel in 3.11.x version

2019-09-06 Thread Jai Bheemsen Rao Dhanwada
Thanks Allen, This works, is there any documentation that explain about all the available logging levels? On Fri, Sep 6, 2019 at 12:07 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thanks, I will try that. > > Is this changed between 2.1.16 to 3.11.3? > > On Thursday, September

Re: Is it possible to build multi cloud cluster for Cassandra

2019-09-06 Thread Devopam Mittra
I will recommend against this idea. And here is why (at a higher level of abstraction) 1. This means the cloud services aren't reliable in the first place. That itself is a big problem. Else with reliability guarantees and multi-region/zone it should be pretty safe to stay in one place. 2. Devil is

Re: Cassandra JVM configuration

2019-09-06 Thread Oleksandr Shulgin
On Fri, Sep 6, 2019 at 11:00 AM wrote: > - reads => as much as possible - huge stream of requests > - data => 186GB on each node > - the reads are unpredictable > - there's (in the cluster) about 6 billions of records > I wonder though, if it makes sense to use Cassandra for a read-only dataset?

Re: Cassandra JVM configuration

2019-09-06 Thread pat
- reads => as much as possible - huge stream of requests - data => 186GB on each node - the reads are unpredictable - there's (in the cluster) about 6 billions of records I'll try change the garbage collector. Thanks Pat On 2019-09-05 16:38, Jeff Jirsa wrote: Lot of variables - how many rea

Re: Cassandra JVM configuration

2019-09-06 Thread pat
Thanks for suggestion. Pat On 2019-09-05 16:19, ZAIDI, ASAD wrote: Every use case is unique so as such jvm configs go with it. 8G may or may not be sufficient depending on live data you keep in, or fetch to memory. You can opt using G1GC, that is easy to start with. Some good suggestions are

Re: Cassandra loglevel in 3.11.x version

2019-09-06 Thread Jai Bheemsen Rao Dhanwada
Thanks, I will try that. Is this changed between 2.1.16 to 3.11.3? On Thursday, September 5, 2019, Inquistive allen wrote: > Hello Jai, > > If you want to fetch queries from the logs. > > Kindly run the below command: > > nodetool setlogginglevel org.apache.cassandra.transport TRACE > > this wi