Re: Cassandra loglevel in 3.11.x version

[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 DEBUG logs to
debug.logs, only when I set the loglevel to DEBUG?

Here is my logback.xml 

Thanks in advance.

On Fri, Sep 6, 2019 at 4:01 PM Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:

> 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, 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 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 will help you see all your queries in logs.
 Just beware that this fills up logs really fast.

 Thanks,
 Allen

 On Fri, 6 Sep, 2019, 10:57 AM Jai Bheemsen Rao Dhanwada, <
 jaibheem...@gmail.com> wrote:

> Hello,
>
> I am trying to enable debug logs on the Cassandra cluster running with
> 3.11.3, I do see some debug logs but I don't see the same level of DEBUG
> logs I used to see with 2.1.16 version of cassandra.
>
> I am using the below command to set debug logging.
>
> $ nodetool setlogginglevel org.apache.cassandra DEBUG
>
>
> In the 2.1.16 version of Cassandra I see the below logs when I make a
> select query using CQL, but I don't see the same trace logs in 3.11.3. has
> anything changed in the 3.11.3 version?
>
>> DEBUG [SharedPool-Worker-1] 2019-09-06 03:43:10,593 Message.java:437
>> - Received: QUERY SELECT * FROM ks.cf WHERE key=? AND id=?;, v=3
>
>
> Thanks in advance.
>

Re: Cassandra loglevel in 3.11.x version

[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, 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 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 will help you see all your queries in logs.
>>> Just beware that this fills up logs really fast.
>>>
>>> Thanks,
>>> Allen
>>>
>>> On Fri, 6 Sep, 2019, 10:57 AM Jai Bheemsen Rao Dhanwada, <
>>> jaibheem...@gmail.com> wrote:
>>>
 Hello,

 I am trying to enable debug logs on the Cassandra cluster running with
 3.11.3, I do see some debug logs but I don't see the same level of DEBUG
 logs I used to see with 2.1.16 version of cassandra.

 I am using the below command to set debug logging.

 $ nodetool setlogginglevel org.apache.cassandra DEBUG


 In the 2.1.16 version of Cassandra I see the below logs when I make a
 select query using CQL, but I don't see the same trace logs in 3.11.3. has
 anything changed in the 3.11.3 version?

> DEBUG [SharedPool-Worker-1] 2019-09-06 03:43:10,593 Message.java:437 -
> Received: QUERY SELECT * FROM ks.cf WHERE key=? AND id=?;, v=3


 Thanks in advance.

>>>

Re: Cassandra JVM configuration

[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.

Also, I have no experience tuning G1 over 31G of heap -- the JVM uses 8 byte 
pointers with a 32G+ heap.  You can get a lot of read throughput with a 24G 
heap with a new size fixed at 8-10G, as long as your records aren't all huge 
blobs.

John...

From: p...@xvalheru.org 
Sent: Friday, September 6, 2019 3:00 AM
To: user@cassandra.apache.org 
Cc: Jeff Jirsa 
Subject: Re: Cassandra JVM configuration

- 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 reads per second per machine?
> - how much data per machine?
> - are the reads random or is there a hot working set?
>
> Some of the suggestions online are old.
> CASSANDRA-8150 has some old’ish suggestions if you’re running CMS
> collector. Running > 16G heap should consider using G1GC and that’s
> tuned quite differently. Amy Tobey has a decent (2.1 era) tuning
> guide, I imagine The Last Pickle has one as well (and wouldn’t be
> surprised if Pythian and Instaclustr do too).
>
>
>
>> On Sep 5, 2019, at 7:04 AM, p...@xvalheru.org wrote:
>>
>> Hi,
>>
>> sorry to bring such question, but I want to ask what are the best JVM
>> options for Cassandra node? In solution I'm implementing the Cassandra
>> serves as read-only storage (of course populated at beginning) - the
>> records are not changed in time. Currently each  Cassandra node's VM
>> has this configuration 16CPUs and 64GB of RAM. I've set these JVM
>> options: -Xms4G and -Xmx40G; JDK 1.8.0_221. My question is what's the
>> best size of memory for Cassandra node and if there's any relation
>> between number of CPUs and memory size. When I've searched for an
>> answer I've found that suggested size for node is 8GB of RAM, but I
>> have doubts.
>>
>> Thanks
>>
>> Pat
>>
>> 
>> Freehosting PIPNI - 
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.pipni.cz_=DwIDaQ=z0adcvxXWKG6LAMN6dVEqQ=W9UI0GQq10yOhf5LxSjoITGT9p69DtOfFK_UGgl4kx8=Twi1q-yZbM-7JseysmH7h_XO5CVH_qz-2rZkyrQ27zY=KB8dnJ9Hih2DBTUE5LHJNDQW5jpcUv9GPGwoC-03bmQ=
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: user-h...@cassandra.apache.org
>>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>
> 
> Freehosting PIPNI - 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.pipni.cz_=DwIDaQ=z0adcvxXWKG6LAMN6dVEqQ=W9UI0GQq10yOhf5LxSjoITGT9p69DtOfFK_UGgl4kx8=Twi1q-yZbM-7JseysmH7h_XO5CVH_qz-2rZkyrQ27zY=KB8dnJ9Hih2DBTUE5LHJNDQW5jpcUv9GPGwoC-03bmQ=


Freehosting PIPNI - 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.pipni.cz_=DwIDaQ=z0adcvxXWKG6LAMN6dVEqQ=W9UI0GQq10yOhf5LxSjoITGT9p69DtOfFK_UGgl4kx8=Twi1q-yZbM-7JseysmH7h_XO5CVH_qz-2rZkyrQ27zY=KB8dnJ9Hih2DBTUE5LHJNDQW5jpcUv9GPGwoC-03bmQ=


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra loglevel in 3.11.x version

[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 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 will help you see all your queries in logs.
>> Just beware that this fills up logs really fast.
>>
>> Thanks,
>> Allen
>>
>> On Fri, 6 Sep, 2019, 10:57 AM Jai Bheemsen Rao Dhanwada, <
>> jaibheem...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am trying to enable debug logs on the Cassandra cluster running with
>>> 3.11.3, I do see some debug logs but I don't see the same level of DEBUG
>>> logs I used to see with 2.1.16 version of cassandra.
>>>
>>> I am using the below command to set debug logging.
>>>
>>> $ nodetool setlogginglevel org.apache.cassandra DEBUG
>>>
>>>
>>> In the 2.1.16 version of Cassandra I see the below logs when I make a
>>> select query using CQL, but I don't see the same trace logs in 3.11.3. has
>>> anything changed in the 3.11.3 version?
>>>
 DEBUG [SharedPool-Worker-1] 2019-09-06 03:43:10,593 Message.java:437 -
 Received: QUERY SELECT * FROM ks.cf WHERE key=? AND id=?;, v=3
>>>
>>>
>>> Thanks in advance.
>>>
>>

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

[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 in the details. None of the current cloud providers behave in a
similar manner of operation. Maintenance will become a nightmare.
3. Setting up security and addition/removal of nodes will be tough if not
irritating.
4. Huge cost involved in data transfer across different platforms if not
inherent delay in replication as well.
5. Potential risk of getting into chase situation amounting up to node
failure due to network delays.


Regards
Devopam

Re: Cassandra JVM configuration

[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?  Couldn't you just put it on something like Amazon S3 and be done
with it?

How many rows per partition do you have?  Do you always scan full partition
or you need to restrict results by clustering key?

Regards,
--
Alex

Re: Cassandra JVM configuration

[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 reads per second per machine?
- how much data per machine?
- are the reads random or is there a hot working set?

Some of the suggestions online are old.
CASSANDRA-8150 has some old’ish suggestions if you’re running CMS
collector. Running > 16G heap should consider using G1GC and that’s
tuned quite differently. Amy Tobey has a decent (2.1 era) tuning
guide, I imagine The Last Pickle has one as well (and wouldn’t be
surprised if Pythian and Instaclustr do too).




On Sep 5, 2019, at 7:04 AM, p...@xvalheru.org wrote:

Hi,

sorry to bring such question, but I want to ask what are the best JVM 
options for Cassandra node? In solution I'm implementing the Cassandra 
serves as read-only storage (of course populated at beginning) - the 
records are not changed in time. Currently each  Cassandra node's VM 
has this configuration 16CPUs and 64GB of RAM. I've set these JVM 
options: -Xms4G and -Xmx40G; JDK 1.8.0_221. My question is what's the 
best size of memory for Cassandra node and if there's any relation 
between number of CPUs and memory size. When I've searched for an 
answer I've found that suggested size for node is 8GB of RAM, but I 
have doubts.


Thanks

Pat


Freehosting PIPNI - http://www.pipni.cz/


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org



-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org



Freehosting PIPNI - http://www.pipni.cz/



Freehosting PIPNI - http://www.pipni.cz/


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra JVM configuration

[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 made if you want to try G1GC or stick with
CMS.  Take a look at [
https://tobert.github.io/pages/als-cassandra-21-tuning-guide.html ]



-Original Message-
From: p...@xvalheru.org [mailto:p...@xvalheru.org]
Sent: Thursday, September 05, 2019 9:05 AM
To: User 
Subject: Cassandra JVM configuration

Hi,

sorry to bring such question, but I want to ask what are the best JVM
options for Cassandra node? In solution I'm implementing the Cassandra
serves as read-only storage (of course populated at beginning) - the
records are not changed in time. Currently each  Cassandra node's VM
has this configuration 16CPUs and 64GB of RAM. I've set these JVM
options:
-Xms4G and -Xmx40G; JDK 1.8.0_221. My question is what's the best size
of memory for Cassandra node and if there's any relation between
number of CPUs and memory size. When I've searched for an answer I've
found that suggested size for node is 8GB of RAM, but I have doubts.

Thanks

Pat


Freehosting PIPNI -
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.pipni.cz_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=FsmDztdsVuIKml8IDhdHdg=H2t7NfxXR_c8S_gVHKbkqoJYt2uJNvBvRcQBiEk2beI=OOXUbYzda5jQw9DZVUA4yExJv1gDNPzsxS0yqPlrDqY=


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org



Freehosting PIPNI - http://www.pipni.cz/



Freehosting PIPNI - http://www.pipni.cz/


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra loglevel in 3.11.x version

[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 will help you see all your queries in logs.
> Just beware that this fills up logs really fast.
>
> Thanks,
> Allen
>
> On Fri, 6 Sep, 2019, 10:57 AM Jai Bheemsen Rao Dhanwada, <
> jaibheem...@gmail.com> wrote:
>
>> Hello,
>>
>> I am trying to enable debug logs on the Cassandra cluster running with
>> 3.11.3, I do see some debug logs but I don't see the same level of DEBUG
>> logs I used to see with 2.1.16 version of cassandra.
>>
>> I am using the below command to set debug logging.
>>
>> $ nodetool setlogginglevel org.apache.cassandra DEBUG
>>
>>
>> In the 2.1.16 version of Cassandra I see the below logs when I make a
>> select query using CQL, but I don't see the same trace logs in 3.11.3. has
>> anything changed in the 3.11.3 version?
>>
>>> DEBUG [SharedPool-Worker-1] 2019-09-06 03:43:10,593 Message.java:437 -
>>> Received: QUERY SELECT * FROM ks.cf WHERE key=? AND id=?;, v=3
>>
>>
>> Thanks in advance.
>>
>

Re: Cassandra loglevel in 3.11.x version

[Inquistive allen]

Hello Jai,

If you want to fetch queries from the logs.

Kindly run the below command:

nodetool setlogginglevel org.apache.cassandra.transport TRACE

this will help you see all your queries in logs.
Just beware that this fills up logs really fast.

Thanks,
Allen

On Fri, 6 Sep, 2019, 10:57 AM Jai Bheemsen Rao Dhanwada, <
jaibheem...@gmail.com> wrote:

> Hello,
>
> I am trying to enable debug logs on the Cassandra cluster running with
> 3.11.3, I do see some debug logs but I don't see the same level of DEBUG
> logs I used to see with 2.1.16 version of cassandra.
>
> I am using the below command to set debug logging.
>
> $ nodetool setlogginglevel org.apache.cassandra DEBUG
>
>
> In the 2.1.16 version of Cassandra I see the below logs when I make a
> select query using CQL, but I don't see the same trace logs in 3.11.3. has
> anything changed in the 3.11.3 version?
>
>> DEBUG [SharedPool-Worker-1] 2019-09-06 03:43:10,593 Message.java:437 -
>> Received: QUERY SELECT * FROM ks.cf WHERE key=? AND id=?;, v=3
>
>
> Thanks in advance.
>