Hi All,
Do we have any inbuilt features to log slow\resource heavy queries?
I tried to check data in system_traces.sessions to check current running
sessions but even that does not have any data.
I'm asking this because I can see 2 nodes in my cluster going Out Of Memory
multiple times but we'
). So you can simply:
nodetool stop VIEW_BUILD Or you can hit JMX directly with the
org.apache.cassandra.db:type=CompactionManager mbean's stopCompaction
operation.. All thats really gonna do is set a flag for the view builder to
stop on its next loop.
stackoverflow.com
Thanks,
Dipan Shah
Forgot to add version info. This is on 3.7.
[cqlsh 5.0.1 | Cassandra 3.7 | CQL spec 3.4.2 | Native protocol v4]
Thanks,
Dipan Shah
From: Dipan Shah
Sent: Thursday, February 28, 2019 3:38 PM
To: user@cassandra.apache.org
Subject: MV's stuck in build
he earlier environment whereas I have already
dropped the view on the current environment (and cant experiment much as the
current environment is in production).
I know this is a bit tricky but I'm pretty much stuck over here and thinking of
finding a non-problem
commitlog_segment_size_in_mb to 128 when the node eventually crashed.
3) No I did not try org.apache.cassandra.db:type=CompactionManager but I did
try "nodetool stop" and "nodetool stop VIEW_BUILD".
Thanks,
Dipan Shah
From: Kenneth Brotman
S
ld be sufficient free
space for data migration to the new node.
2) Check logs of the seed nodes and see if there are any errors. I found some
gossip file corruption on one of the seed nodes.
3) Finally, restart server\cassandra services on the seed nodes and see if that
helps.
Do let me know if this s
ld restart all nodes and that seems
to be overkill.
Can someone please guide me through this?
Thanks,
Dipan Shah
his but did not get
anything that matches my scenario.
Please note, I do not get this error when I run the same query from any other
node. And I'm connecting to the node using cqlsh.
Thanks,
Dipan Shah
org.apache.cassandra.streaming.ConnectionHandler$IncomingMessageHandler.run(ConnectionHandler.java:317)
~[apache-cassandra-3.11.0.jar:3.11.0]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]
Thanks,
Dipan Shah
From: kurt greaves
Sent: Wednesday, December 20, 2017 2:23 AM
To: User
0.000.00150 0
Max 0.000.000.0053142810146 1996099046
Thanks,
Dipan Shah
From: Dipan Shah
Sent: Wednesday, December 20, 2017 12:04 PM
To: User
Subject: Re: Error during select query - Found other issues with cluster too
Hello
after that will update if that solved my problem.
Thanks,
Dipan Shah
From: adama.diab...@orange.com
Sent: Wednesday, December 20, 2017 3:43 PM
To: user@cassandra.apache.org; Dipan Shah
Subject: RE: Error during select query - Found other issues with cluster too
e if I can do something about this.
Thanks,
Dipan Shah
From: Nicolas Guyomar
Sent: Wednesday, December 20, 2017 2:48 PM
To: user@cassandra.apache.org
Subject: Re: Error during select query - Found other issues with cluster too
Hi Dipan,
This seems lik
schema.
Thanks,
Dipan Shah
From: onmstester onmstester
Sent: Thursday, March 8, 2018 1:31 PM
To: user
Subject: Re: backup/restore cassandra data
Thanks
But is'nt there a method to restore the node as it was before the crash, like
commitlog and every last
ize to see what happens and that sent the
value of pending tasks back to 0.
I have done this earlier for a similar tables and it has worked perfectly fine
for me. What could have gone wrong over here?
Thanks,
Dipan Shah
Hello lampahome,
Data will be compressed but you will also have to account for the replication
factor that you will be using.
Thanks,
Dipan Shah
From: lampahome
Sent: Tuesday, December 31, 2019 8:06 AM
To: user@cassandra.apache.org
Subject: How bottom of
Hello Sebastien,
Not sure but have you checked the output of "nodetool describecluster"? A
schema mismatch or node unavailability might result in this.
Thanks,
Dipan Shah
From: Sébastien Rebecchi
Sent: Wednesday, May 26, 2021 7:35 P
due to low disk space
* Cassandra will not be able to compact data (and free up space) if it
does not have the required disk space to rewrite files. Check system.log for
compaction error
Thanks,
Dipan Shah
From: Bowen Song
Sent: Friday, September 17, 2021
e with the latest schema changes made in the
cluster.
If this is just a DEBUG\INFO message and not a WARN\ERROR, you can safely
ignore it.
Thanks,
Dipan Shah
From: Joe Obernberger
Sent: Monday, February 13, 2023 9:10 PM
To: user@cassandra.apache.org
Subjec
mes for when we do add
> new nodes?
>
> If we double the network bandwidth can we effectively reduce this lengthy
> cleanup?
>
> Maybe just ignore cleanup entirely?
>
> I appreciate that cleanup will increase the load but running cleanup on
> one node at a time seems impr
write to ONE node for a particular key and have a replication factor
>> of 3, would the written key will get replicated to the other two nodes ?
>> Let me know if I am thinking incorrectly.
>> >
>> > Thanks,
>> > Anurag
>>
>
--
Thanks,
*Dipan Shah*
ease a given threshold?
>
> Best regard
>
> Sébastien
>
--
Thanks,
*Dipan Shah*
*Data Engineer*
[image: https://www.anant.us/Home.aspx]
3 Washington Circle NW, Suite 301
Washington, D.C. 20037
*Check out our **blog* <https://blog.anant.us/>*!*
This email and any attachments
Hello Sebastien,
There are no inbuilt tools that will automatically remove folders of deleted
tables.
Thanks,
Dipan Shah
From: Sébastien Rebecchi
Sent: 04 December 2023 13:54
To: user@cassandra.apache.org
Subject: Remove folders of deleted tables
Hello
22 matches
Mail list logo
