Re: Snapshot SSTable modified??

[Max C]

I looked at the source code for GNU tar, and it looks for a change in the 
create time or (more likely) a change in the size.

This seems very strange to me — I would think that creating a snapshot would 
cause a flush and then once the SSTables are written, hardlinks would be 
created and the SSTables wouldn't be written to after that.

Our solution is to wait 5 minutes and retry the tar if an error occurs.  This 
isn't ideal - but it's the best I could come up with.  :-/

Thanks Jeff & others for your responses.

- Max

> On May 25, 2018, at 5:05pm, Elliott Sims  wrote:
> 
> I've run across this problem before - it seems like GNU tar interprets 
> changes in the link count as changes to the file, so if the file gets 
> compacted mid-backup it freaks out even if the file contents are unchanged.  
> I worked around it by just using bsdtar instead.
> 
> On Thu, May 24, 2018 at 6:08 AM, Nitan Kainth  > wrote:
> Jeff,
> 
> Shouldn't Snapshot get consistent state of sstables? -tmp file shouldn't 
> impact backup operation right?
> 
> 
> Regards,
> Nitan K.
> Cassandra and Oracle Architect/SME
> Datastax Certified Cassandra expert
> Oracle 10g Certified
> 
> On Wed, May 23, 2018 at 6:26 PM, Jeff Jirsa  > wrote:
> In versions before 3.0, sstables were written with a -tmp filename and 
> copied/moved to the final filename when complete. This changes in 3.0 - we 
> write into the file with the final name, and have a journal/log to let uss 
> know when it's done/final/live.
> 
> Therefore, you can no longer just watch for a -Data.db file to be created and 
> uploaded - you have to watch the log to make sure it's not being written.
> 
> 
> On Wed, May 23, 2018 at 2:18 PM, Max C.  > wrote:
> Hi Everyone,
> 
> We’ve noticed a few times in the last few weeks that when we’re doing 
> backups, tar has complained with messages like this:
> 
> tar: 
> /var/lib/cassandra/data/mars/test_instances_by_test_id-6a9440a04cc111e8878675f1041d7e1c/snapshots/backup_20180523_024502/mb-63-big-Data.db:
>  file changed as we read it
> 
> Any idea what might be causing this?
> 
> We’re running Cassandra 3.0.8 on RHEL 7.  Here’s rough pseudocode of our 
> backup process:
> 
> 
> SNAPSHOT_NAME=backup_YYYMMDD_HHMMSS
> nodetool snapshot -t $SNAPSHOT_NAME
> 
> for each keyspace
> - dump schema to “schema.cql"
> - tar -czf /file_server/backup_$HOSTNAME_$KEYSPACE_MMDD_HHMMSS.tgz 
> schema.cql /var/lib/cassandra/data/$KEYSPACE/*/snapshots/$SNAPSHOT_NAME
> 
> nodetool clearsnapshot -t $SNAPSHOT_NAME
> 
> Thanks.
> 
> - Max
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org 
> 
> For additional commands, e-mail: user-h...@cassandra.apache.org 
> 
> 
> 
> 
> 

Re: Snapshot SSTable modified??

[Elliott Sims]

I've run across this problem before - it seems like GNU tar interprets
changes in the link count as changes to the file, so if the file gets
compacted mid-backup it freaks out even if the file contents are
unchanged.  I worked around it by just using bsdtar instead.

On Thu, May 24, 2018 at 6:08 AM, Nitan Kainth  wrote:

> Jeff,
>
> Shouldn't Snapshot get consistent state of sstables? -tmp file shouldn't
> impact backup operation right?
>
>
> Regards,
> Nitan K.
> Cassandra and Oracle Architect/SME
> Datastax Certified Cassandra expert
> Oracle 10g Certified
>
> On Wed, May 23, 2018 at 6:26 PM, Jeff Jirsa  wrote:
>
>> In versions before 3.0, sstables were written with a -tmp filename and
>> copied/moved to the final filename when complete. This changes in 3.0 - we
>> write into the file with the final name, and have a journal/log to let uss
>> know when it's done/final/live.
>>
>> Therefore, you can no longer just watch for a -Data.db file to be created
>> and uploaded - you have to watch the log to make sure it's not being
>> written.
>>
>>
>> On Wed, May 23, 2018 at 2:18 PM, Max C.  wrote:
>>
>>> Hi Everyone,
>>>
>>> We’ve noticed a few times in the last few weeks that when we’re doing
>>> backups, tar has complained with messages like this:
>>>
>>> tar: /var/lib/cassandra/data/mars/test_instances_by_test_id-6a944
>>> 0a04cc111e8878675f1041d7e1c/snapshots/backup_20180523_024502/mb-63-big-Data.db:
>>> file changed as we read it
>>>
>>> Any idea what might be causing this?
>>>
>>> We’re running Cassandra 3.0.8 on RHEL 7.  Here’s rough pseudocode of our
>>> backup process:
>>>
>>> 
>>> SNAPSHOT_NAME=backup_YYYMMDD_HHMMSS
>>> nodetool snapshot -t $SNAPSHOT_NAME
>>>
>>> for each keyspace
>>> - dump schema to “schema.cql"
>>> - tar -czf /file_server/backup_$HOSTNAME_$KEYSPACE_MMDD_HHMMSS.tgz
>>> schema.cql /var/lib/cassandra/data/$KEYSPACE/*/snapshots/$SNAPSHOT_NAME
>>>
>>> nodetool clearsnapshot -t $SNAPSHOT_NAME
>>>
>>> Thanks.
>>>
>>> - Max
>>> -
>>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>>> For additional commands, e-mail: user-h...@cassandra.apache.org
>>>
>>>
>>
>

Re: EXT: Cassandra Monitoring tool

[Rahul Singh]

Good article about it on LI

https://www.linkedin.com/pulse/snap-cassandra-s3-tablesnap-vijaya-kumar-hosamani/

On May 25, 2018, 2:52 PM -0500, Joaquin Casares , 
wrote:
> Hello Aneesh,
>
> While this doesn't provide a GUI, tablesnap is a community tool that does a 
> great job at handling backups:
>
> > https://github.com/JeremyGrosser/tablesnap
>
> Cheers,
>
> Joaquin
>
> Joaquin Casares
> Consultant
> Austin, TX
>
> Apache Cassandra Consulting
> http://www.thelastpickle.com
>
> > On Fri, May 25, 2018 at 11:36 AM, ANEESH KUMAR K.M  
> > wrote:
> > > Thank you Hari for the details.
> > >
> > > One more question, please suggest me some cluster managing too for 
> > > Cassandra cluster. Looking for opensource tools that will support to take 
> > > snapshot and restore via GUI.
> > >
> > > Regards,
> > > Aneesh
> > >
> > > > On Fri, May 25, 2018 at 10:00 PM, Harikrishnan Pillai 
> > > >  wrote:
> > > > > I assume you are using open source cassandra and you can look at 
> > > > > Prometheus grafana for cassandra monitoring and lot information 
> > > > > available in internet regarding how to setup the Prometheus 
> > > > > monitoring for cassandra .
> > > > >
> > > > >
> > > > > Sent from my iPhone
> > > > >
> > > > > > On May 25, 2018, at 9:23 AM, ANEESH KUMAR K.M  
> > > > > > wrote:
> > > > > >
> > > > > > Please suggest me some good cluster monitoring tool for cassandra 
> > > > > > multi region cluster.
> > > > > >
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> > > > > For additional commands, e-mail: user-h...@cassandra.apache.org
> > > > >
> > >
>

Re: EXT: Cassandra Monitoring tool

[Joaquin Casares]

Hello Aneesh,

While this doesn't provide a GUI, tablesnap is a community tool that does a
great job at handling backups:

https://github.com/JeremyGrosser/tablesnap


Cheers,

Joaquin

Joaquin Casares
Consultant
Austin, TX

Apache Cassandra Consulting
http://www.thelastpickle.com

On Fri, May 25, 2018 at 11:36 AM, ANEESH KUMAR K.M 
wrote:

> Thank you Hari for the details.
>
> One more question, please suggest me some cluster managing too for
> Cassandra cluster. Looking for opensource tools that will support to take
> snapshot and restore via GUI.
>
> Regards,
> Aneesh
>
> On Fri, May 25, 2018 at 10:00 PM, Harikrishnan Pillai <
> hpil...@walmartlabs.com> wrote:
>
>> I assume you are using open source cassandra and you can look at
>> Prometheus grafana for cassandra monitoring and lot information available
>> in internet regarding how to setup the Prometheus monitoring for cassandra .
>>
>>
>> Sent from my iPhone
>>
>> > On May 25, 2018, at 9:23 AM, ANEESH KUMAR K.M 
>> wrote:
>> >
>> > Please suggest me some good cluster monitoring tool for cassandra multi
>> region cluster.
>> >
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: user-h...@cassandra.apache.org
>>
>>
>

Re: Log application Queries

[Nitan Kainth]

this is awesome Jeff.


Regards,
Nitan K.
Cassandra and Oracle Architect/SME
Datastax Certified Cassandra expert
Oracle 10g Certified

On Fri, May 25, 2018 at 3:00 PM, Jeff Jirsa  wrote:

> https://issues.apache.org/jira/browse/CASSANDRA-13983 was added to
> cassandra 4.0
>
>
>
> On Fri, May 25, 2018 at 8:24 AM, Nitan Kainth 
> wrote:
>
>> Hi,
>>
>> I would like to log all C* queries hitting cluster. Could someone please
>> tell me how can I do it at cluster level?
>> Will nodetool setlogginglevel work? If so, please share example with
>> library name.
>>
>> C* version 3.11
>>
>
>

Re: Log application Queries

[Jeff Jirsa]

https://issues.apache.org/jira/browse/CASSANDRA-13983 was added to
cassandra 4.0



On Fri, May 25, 2018 at 8:24 AM, Nitan Kainth  wrote:

> Hi,
>
> I would like to log all C* queries hitting cluster. Could someone please
> tell me how can I do it at cluster level?
> Will nodetool setlogginglevel work? If so, please share example with
> library name.
>
> C* version 3.11
>

Re: Log application Queries

[Nitan Kainth]

Thanks Alain


Regards,
Nitan K.
Cassandra and Oracle Architect/SME
Datastax Certified Cassandra expert
Oracle 10g Certified

On Fri, May 25, 2018 at 2:05 PM, Alain RODRIGUEZ  wrote:

> Nate wrote a post about this exact topic. In case it is of some use:
> http://thelastpickle.com/blog/2016/02/10/locking-down-
> apache-cassandra-logging.html
>
> C*heers,
> ---
> Alain Rodriguez - @arodream - al...@thelastpickle.com
> France / Spain
>
> The Last Pickle - Apache Cassandra Consulting
> http://www.thelastpickle.com
>
> 2018-05-25 18:00 GMT+01:00 Nitan Kainth :
>
>> So settraceprobability is better option than nodetool :)
>>
>>
>> Regards,
>> Nitan K.
>> Cassandra and Oracle Architect/SME
>> Datastax Certified Cassandra expert
>> Oracle 10g Certified
>>
>> On Fri, May 25, 2018 at 12:15 PM, Surbhi Gupta 
>> wrote:
>>
>>> nodeool setlogginglevel is only valid for below :
>>>
>>>
>>>- org.apache.cassandra
>>>- org.apache.cassandra.db
>>>- org.apache.cassandra.service.StorageProxy
>>>
>>>
>>> On 25 May 2018 at 09:01, Nitan Kainth  wrote:
>>>
 Thanks Surbhi. I found another way. I used nodetool
 settraceprobability 1 and it is logging in system_traces.

 How is it different from nodeool setlogginglevel?


 Regards,
 Nitan K.
 Cassandra and Oracle Architect/SME
 Datastax Certified Cassandra expert
 Oracle 10g Certified

 On Fri, May 25, 2018 at 11:41 AM, Surbhi Gupta <
 surbhi.gupt...@gmail.com> wrote:

> If using dse then u can enable in dse.yaml.
>
> # CQL slow log settings
> cql_slow_log_options:
> enabled: true
> threshold_ms: 0
> ttl_seconds: 259200
>
> As far as my understanding says setlogginglevel  is used for changing
> the logging level as below but not for slow query .
>
>- ALL
>- TRACE
>- DEBUG
>- INFO
>- WARN
>- ERROR
>- OFF
>
>
>
> On 25 May 2018 at 08:24, Nitan Kainth  wrote:
>
>> Hi,
>>
>> I would like to log all C* queries hitting cluster. Could someone
>> please tell me how can I do it at cluster level?
>> Will nodetool setlogginglevel work? If so, please share example with
>> library name.
>>
>> C* version 3.11
>>
>
>

>>>
>>
>

Re: Log application Queries

[Alain RODRIGUEZ]

Nate wrote a post about this exact topic. In case it is of some use:
http://thelastpickle.com/blog/2016/02/10/locking-down-apache-cassandra-logging.html

C*heers,
---
Alain Rodriguez - @arodream - al...@thelastpickle.com
France / Spain

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2018-05-25 18:00 GMT+01:00 Nitan Kainth :

> So settraceprobability is better option than nodetool :)
>
>
> Regards,
> Nitan K.
> Cassandra and Oracle Architect/SME
> Datastax Certified Cassandra expert
> Oracle 10g Certified
>
> On Fri, May 25, 2018 at 12:15 PM, Surbhi Gupta 
> wrote:
>
>> nodeool setlogginglevel is only valid for below :
>>
>>
>>- org.apache.cassandra
>>- org.apache.cassandra.db
>>- org.apache.cassandra.service.StorageProxy
>>
>>
>> On 25 May 2018 at 09:01, Nitan Kainth  wrote:
>>
>>> Thanks Surbhi. I found another way. I used nodetool settraceprobability
>>> 1 and it is logging in system_traces.
>>>
>>> How is it different from nodeool setlogginglevel?
>>>
>>>
>>> Regards,
>>> Nitan K.
>>> Cassandra and Oracle Architect/SME
>>> Datastax Certified Cassandra expert
>>> Oracle 10g Certified
>>>
>>> On Fri, May 25, 2018 at 11:41 AM, Surbhi Gupta >> > wrote:
>>>
 If using dse then u can enable in dse.yaml.

 # CQL slow log settings
 cql_slow_log_options:
 enabled: true
 threshold_ms: 0
 ttl_seconds: 259200

 As far as my understanding says setlogginglevel  is used for changing
 the logging level as below but not for slow query .

- ALL
- TRACE
- DEBUG
- INFO
- WARN
- ERROR
- OFF



 On 25 May 2018 at 08:24, Nitan Kainth  wrote:

> Hi,
>
> I would like to log all C* queries hitting cluster. Could someone
> please tell me how can I do it at cluster level?
> Will nodetool setlogginglevel work? If so, please share example with
> library name.
>
> C* version 3.11
>


>>>
>>
>

Re: Cassandra Monitoring tool

[Joaquin Casares]

Hello Aneesh,

Alain and I also worked on this project that you might find useful:

https://github.com/thelastpickle/docker-cassandra-bootstrap


It is a Docker Compose environment to showcase the Prometheus graphs that
we worked on. There's still a missing update, so do please check back soon,
but the majority of what we've worked on is housed in that repo. If you
decide to move forward with Prometheus, you can use the curl scripts
provided in the repo to upload the charts and all preset alerts into your
Grafana environment. If you use the GUI to upload the graphs, you'll lose
all preset visual thresholds and alerts, but still keep all completed
tooltips/descriptions.

Now that I remembered it was missing an update, we should push the new
features out sooner rather than later. The new update includes better
descriptive text, alert text, and alert fixes.

Hope it helps!

Joaquin

Joaquin Casares
Consultant
Austin, TX

Apache Cassandra Consulting
http://www.thelastpickle.com

On Fri, May 25, 2018 at 12:54 PM, Alain RODRIGUEZ 
wrote:

> Hello,
>
> With more details on your criteria, it would be easier.
>
> I used:
>
> - SPM from Sematext (Commercial - dashboards out of the box)
> - Datastax OpsCenter (Commercial, With DSE only nowadays)
> - Grafana/Graphite or Prometheus (Open source - 'do it yourself' - but
> some templates exist)
> - Datadog (Commercial - dashboards out of the box)
>
> It depends what you want really. All those worked for me at some point in
> time :).
>
> Note: We built the Dashboards that are out of the box for Datadog. I
> believe it should put anyone starting with Cassandra in good conditions to
> operate and troubleshot Apache Cassandra. My opinion here is biased most
> definitely :). I liked the interfaces of Datadog (using regularly) and
> Sematext (old experience) the most.
>
> C*heers,
> ---
> Alain Rodriguez - @arodream - al...@thelastpickle.com
> France / Spain
>
> The Last Pickle - Apache Cassandra Consulting
> http://www.thelastpickle.com
>
> 2018-05-25 17:23 GMT+01:00 ANEESH KUMAR K.M :
>
>> Please suggest me some good cluster monitoring tool for cassandra multi
>> region cluster.
>>
>>
>

Re: Cassandra Monitoring tool

[Alain RODRIGUEZ]

Hello,

With more details on your criteria, it would be easier.

I used:

- SPM from Sematext (Commercial - dashboards out of the box)
- Datastax OpsCenter (Commercial, With DSE only nowadays)
- Grafana/Graphite or Prometheus (Open source - 'do it yourself' - but some
templates exist)
- Datadog (Commercial - dashboards out of the box)

It depends what you want really. All those worked for me at some point in
time :).

Note: We built the Dashboards that are out of the box for Datadog. I
believe it should put anyone starting with Cassandra in good conditions to
operate and troubleshot Apache Cassandra. My opinion here is biased most
definitely :). I liked the interfaces of Datadog (using regularly) and
Sematext (old experience) the most.

C*heers,
---
Alain Rodriguez - @arodream - al...@thelastpickle.com
France / Spain

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2018-05-25 17:23 GMT+01:00 ANEESH KUMAR K.M :

> Please suggest me some good cluster monitoring tool for cassandra multi
> region cluster.
>
>

Re: unsubscribe

[Alain RODRIGUEZ]

Hello Matthias,

I don't think you really left :). Give this address a try instead:
user-unsubscr...@cassandra.apache.org

;-)

C*iao,

2018-05-24 23:37 GMT+01:00 Matthias Hübner :

> Ciao
>

Re: Reading Data from C* Cluster

[Alain RODRIGUEZ]

Hello,

Where I can have configurable codes in partition key as cassandra supports.
>

I am sorry I don't understand this.

1) How much data I can put in one partition ?
>

Well, Cassandra supports huge partitions. In practice, the value of 100 MB
per partition is often shared. I consider it's a good 'soft' limit.
Basically, with such a small table/strings combination, you will probably
not reach limits any time soon unless the workload is really intensive. The
hard limit is kind of irrelevant I would say, Cassandra will be working
poorly before reaching it that the precise value does not matter much.

Nonetheless, make sure to pick a good partition key. A good partition key
should be ideally, meaningful and allow you to retrieve all the data you
need querying one partition (or just a few). A good partition key should
also allow the partitions/rows to all have a similar size (as much as
possible) and to be distributed evenly in the token ring as well (using a
date as the partition key for example, will induce all the request for this
date to only hit a small portion of the servers - 1 server and its replica
only). All the fragments of the same partition go to 1 node (and to the
corresponding replicas). It is easy to create imbalances.

It is really important to pick this key appropriately considering these
best practices/constraints.

2) I want to read data from cassandra as
> SELECT * from code where campaign_id_sub_partition = 'XXX-1';
> Is reading whole partition at one time is feasible or shall I use
> pagination ?
>

 I would make sure to use a client that uses pagination under the hood.
Modern clients do it for you. Depending on the size of the partition, the
pagination will be useless, nice to have or mandatory not to reach the
timeout. But I would really try not to implement this and pick some client
that do that already.

C*heers,
---
Alain Rodriguez - @arodream - al...@thelastpickle.com
France / Spain

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com


2018-05-24 19:55 GMT+01:00 raman gugnani :

> HI
>
> I want to read data from C* Cluster.
>
> Schema is
>
> CREATE TABLE code(
> campaign_id_sub_partition text
> code text,
> PRIMARY KEY ((campaign_id_sub_partition),code))
> );
>
> Where I can have configurable codes in partition key as cassandra supports.
> campaign_id_sub_partition is appx 10 characters
> code field is appx 12~20 characters
>
>
> Query :
> 1) How much data I can put in one partition ?
>
> 2) I want to read data from cassandra as
> SELECT * from code where campaign_id_sub_partition = 'XXX-1';
> Is reading whole partition at one time is feasible or shall I use
> pagination ?
>
> --
> Raman Gugnani
>
> 8588892293
>
>

Re: Log application Queries

[Nitan Kainth]

So settraceprobability is better option than nodetool :)


Regards,
Nitan K.
Cassandra and Oracle Architect/SME
Datastax Certified Cassandra expert
Oracle 10g Certified

On Fri, May 25, 2018 at 12:15 PM, Surbhi Gupta 
wrote:

> nodeool setlogginglevel is only valid for below :
>
>
>- org.apache.cassandra
>- org.apache.cassandra.db
>- org.apache.cassandra.service.StorageProxy
>
>
> On 25 May 2018 at 09:01, Nitan Kainth  wrote:
>
>> Thanks Surbhi. I found another way. I used nodetool settraceprobability
>> 1 and it is logging in system_traces.
>>
>> How is it different from nodeool setlogginglevel?
>>
>>
>> Regards,
>> Nitan K.
>> Cassandra and Oracle Architect/SME
>> Datastax Certified Cassandra expert
>> Oracle 10g Certified
>>
>> On Fri, May 25, 2018 at 11:41 AM, Surbhi Gupta 
>> wrote:
>>
>>> If using dse then u can enable in dse.yaml.
>>>
>>> # CQL slow log settings
>>> cql_slow_log_options:
>>> enabled: true
>>> threshold_ms: 0
>>> ttl_seconds: 259200
>>>
>>> As far as my understanding says setlogginglevel  is used for changing
>>> the logging level as below but not for slow query .
>>>
>>>- ALL
>>>- TRACE
>>>- DEBUG
>>>- INFO
>>>- WARN
>>>- ERROR
>>>- OFF
>>>
>>>
>>>
>>> On 25 May 2018 at 08:24, Nitan Kainth  wrote:
>>>
 Hi,

 I would like to log all C* queries hitting cluster. Could someone
 please tell me how can I do it at cluster level?
 Will nodetool setlogginglevel work? If so, please share example with
 library name.

 C* version 3.11

>>>
>>>
>>
>

Re: EXT: Cassandra Monitoring tool

[ANEESH KUMAR K.M]

Thank you Hari for the details.

One more question, please suggest me some cluster managing too for
Cassandra cluster. Looking for opensource tools that will support to take
snapshot and restore via GUI.

Regards,
Aneesh

On Fri, May 25, 2018 at 10:00 PM, Harikrishnan Pillai <
hpil...@walmartlabs.com> wrote:

> I assume you are using open source cassandra and you can look at
> Prometheus grafana for cassandra monitoring and lot information available
> in internet regarding how to setup the Prometheus monitoring for cassandra .
>
>
> Sent from my iPhone
>
> > On May 25, 2018, at 9:23 AM, ANEESH KUMAR K.M  wrote:
> >
> > Please suggest me some good cluster monitoring tool for cassandra multi
> region cluster.
> >
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>

Re: EXT: Cassandra Monitoring tool

[Harikrishnan Pillai]

I assume you are using open source cassandra and you can look at Prometheus 
grafana for cassandra monitoring and lot information available in internet 
regarding how to setup the Prometheus monitoring for cassandra .


Sent from my iPhone

> On May 25, 2018, at 9:23 AM, ANEESH KUMAR K.M  wrote:
> 
> Please suggest me some good cluster monitoring tool for cassandra multi 
> region cluster.
> 

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

Cassandra Monitoring tool

[ANEESH KUMAR K.M]

Please suggest me some good cluster monitoring tool for cassandra multi
region cluster.

Re: Log application Queries

[Surbhi Gupta]

nodeool setlogginglevel is only valid for below :


   - org.apache.cassandra
   - org.apache.cassandra.db
   - org.apache.cassandra.service.StorageProxy


On 25 May 2018 at 09:01, Nitan Kainth  wrote:

> Thanks Surbhi. I found another way. I used nodetool settraceprobability 1
> and it is logging in system_traces.
>
> How is it different from nodeool setlogginglevel?
>
>
> Regards,
> Nitan K.
> Cassandra and Oracle Architect/SME
> Datastax Certified Cassandra expert
> Oracle 10g Certified
>
> On Fri, May 25, 2018 at 11:41 AM, Surbhi Gupta 
> wrote:
>
>> If using dse then u can enable in dse.yaml.
>>
>> # CQL slow log settings
>> cql_slow_log_options:
>> enabled: true
>> threshold_ms: 0
>> ttl_seconds: 259200
>>
>> As far as my understanding says setlogginglevel  is used for changing
>> the logging level as below but not for slow query .
>>
>>- ALL
>>- TRACE
>>- DEBUG
>>- INFO
>>- WARN
>>- ERROR
>>- OFF
>>
>>
>>
>> On 25 May 2018 at 08:24, Nitan Kainth  wrote:
>>
>>> Hi,
>>>
>>> I would like to log all C* queries hitting cluster. Could someone please
>>> tell me how can I do it at cluster level?
>>> Will nodetool setlogginglevel work? If so, please share example with
>>> library name.
>>>
>>> C* version 3.11
>>>
>>
>>
>

Re: Log application Queries

[Nitan Kainth]

Thanks Surbhi. I found another way. I used nodetool settraceprobability 1
and it is logging in system_traces.

How is it different from nodeool setlogginglevel?


Regards,
Nitan K.
Cassandra and Oracle Architect/SME
Datastax Certified Cassandra expert
Oracle 10g Certified

On Fri, May 25, 2018 at 11:41 AM, Surbhi Gupta 
wrote:

> If using dse then u can enable in dse.yaml.
>
> # CQL slow log settings
> cql_slow_log_options:
> enabled: true
> threshold_ms: 0
> ttl_seconds: 259200
>
> As far as my understanding says setlogginglevel  is used for changing the
> logging level as below but not for slow query .
>
>- ALL
>- TRACE
>- DEBUG
>- INFO
>- WARN
>- ERROR
>- OFF
>
>
>
> On 25 May 2018 at 08:24, Nitan Kainth  wrote:
>
>> Hi,
>>
>> I would like to log all C* queries hitting cluster. Could someone please
>> tell me how can I do it at cluster level?
>> Will nodetool setlogginglevel work? If so, please share example with
>> library name.
>>
>> C* version 3.11
>>
>
>

Re: Log application Queries

[Surbhi Gupta]

If using dse then u can enable in dse.yaml.

# CQL slow log settings
cql_slow_log_options:
enabled: true
threshold_ms: 0
ttl_seconds: 259200

As far as my understanding says setlogginglevel  is used for changing the
logging level as below but not for slow query .

   - ALL
   - TRACE
   - DEBUG
   - INFO
   - WARN
   - ERROR
   - OFF



On 25 May 2018 at 08:24, Nitan Kainth  wrote:

> Hi,
>
> I would like to log all C* queries hitting cluster. Could someone please
> tell me how can I do it at cluster level?
> Will nodetool setlogginglevel work? If so, please share example with
> library name.
>
> C* version 3.11
>

Log application Queries

[Nitan Kainth]

Hi,

I would like to log all C* queries hitting cluster. Could someone please
tell me how can I do it at cluster level?
Will nodetool setlogginglevel work? If so, please share example with
library name.

C* version 3.11