Thanks!
On Friday, July 19, 2019, 10:15:43 PM GMT+3, Jon Haddad
wrote:
It's a limit on the total compaction throughput.
On Fri, Jul 19, 2019 at 10:39 AM Vlad wrote:
Hi,
is 'nodetool setcompactionthroughput' sets limit for all compactions on the
node, or is it per compaction thread
It's a limit on the total compaction throughput.
On Fri, Jul 19, 2019 at 10:39 AM Vlad wrote:
> Hi,
>
> is 'nodetool setcompactionthroughput' sets limit for all compactions on
> the node, or is it per compaction thread?
>
> Thanks.
>
Sorry no corruption errors.
Thanks Jeff,
Anything specific to look into if this happens again
On Fri, Jul 19, 2019, 2:40 PM Nitan Kainth wrote:
> You no corruption error or you see corruption error?
>
>
> Regards,
>
> Nitan
>
> Cell: 510 449 9629
>
> On Jul 19, 2019, at 1:52 PM, Rahul Reddy
You no corruption error or you see corruption error?
Regards,
Nitan
Cell: 510 449 9629
> On Jul 19, 2019, at 1:52 PM, Rahul Reddy wrote:
>
> Schema matches and corruption errors in system.log
>
>> On Fri, Jul 19, 2019, 1:33 PM Nitan Kainth wrote:
>> Do you see schemat in sync? Nodetool descr
Schema matches and corruption errors in system.log
On Fri, Jul 19, 2019, 1:33 PM Nitan Kainth wrote:
> Do you see schemat in sync? Nodetool describecluster.
>
> Check system log for any corruption.
>
>
> Regards,
>
> Nitan
>
> Cell: 510 449 9629
>
> On Jul 19, 2019, at 12:32 PM, ZAIDI, ASAD A w
Hi,
is 'nodetool setcompactionthroughput' sets limit for all compactions on the
node, or is it per compaction thread?
Thanks.
Do you see schemat in sync? Nodetool describecluster.
Check system log for any corruption.
Regards,
Nitan
Cell: 510 449 9629
> On Jul 19, 2019, at 12:32 PM, ZAIDI, ASAD A wrote:
>
> “aws asked to set nvme_timeout to higher number in etc/grub.conf.”
>
> Did you ask AWS if setting higher valu
Could be something like
https://issues.apache.org/jira/browse/CASSANDRA-14358
Hard to say after the fact.
On Fri, Jul 19, 2019 at 8:49 AM Rahul Reddy
wrote:
> Here ,
>
> We have 6 nodes each in 2 data centers us-east-1 and us-west-2 . We have
> RF 3 and cl set to local quorum. And gossip sni
https://lore.kernel.org/patchwork/patch/884501/
according to this link , it sound like having patched kernel is real solution
to bug
From: Rahul Reddy [mailto:rahulreddy1...@gmail.com]
Sent: Friday, July 19, 2019 11:48 AM
To: user@cassandra.apache.org
Subject: Re: Rebooting one Cassandra node
Hello Rahul,
As per your description, Cassandra process is up and running as you
verified from the logs.
But nodetool and grafana arnt fetching data.
This points to the suspect being jmx port 7199.
Do run and check 'netstat -anp | egrep"7199|9042|7070" ' on the impacted
and other hosts in the clu
“aws asked to set nvme_timeout to higher number in etc/grub.conf.”
Did you ask AWS if setting higher value is real solution to bug - Is there not
any patch available to address the bug? - just curios to know
From: Rahul Reddy [mailto:rahulreddy1...@gmail.com]
Sent: Friday, July 19, 2019 10:49
Hello Rahul,
Basically the issue is running nodetool status on the host rebooted node,
shows itself as UN and all other nodes in the cluster as DN.
And running nodetool status on any other node in the cluster shows this
rebooted node as DN.
Correct me if I am wrong. Is this the issue.
Also attach
Thanks for quick response rajshekar.
Correct same cassandra.yml and same java
On Fri, Jul 19, 2019, 11:56 AM Rajsekhar Mallick
wrote:
> Hello Rahul,
>
> May you please confirm on below things.
>
> 1. Cassandra.yaml file of the node which was started after the machine
> reboot is same as that of
Hello Rahul,
May you please confirm on below things.
1. Cassandra.yaml file of the node which was started after the machine
reboot is same as that of rest of the nodes in the cluster.
2. Java version is consistent across all nodes in the cluster.
Do check and revert
Thanks
On Fri, 19 Jul, 2019
Here ,
We have 6 nodes each in 2 data centers us-east-1 and us-west-2 . We have
RF 3 and cl set to local quorum. And gossip snitch. All our instance are
c5.2xlarge and data files and comit logs are stored in gp2 ebs. C5
instance type had a bug which aws asked to set nvme_timeout to higher
numbe
Hi Rajsekhar,
Here the details:
1)
[cassadm@bipcas00 ~]$ nodetool tablestats tims.MESSAGE_HISTORY
Total number of tables: 259
Keyspace : tims
Read Count: 208256144
Read Latency: 7.655146714749506 ms
Write Count: 2218205275
Write Latency: 1.7826005
16 matches
Mail list logo
