cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Otto (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13663) Cassandra 3.10 crashes without dump
Date Fri, 04 Aug 2017 08:26:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114106#comment-16114106
] 

Matthias Otto commented on CASSANDRA-13663:
-------------------------------------------

We have been able to find additional information that seems to pertain to this task. From
what we have been able to see via our newly implemented ram monitoring, the servers very slowly
take up more and more of the available ram until there is no more free ram on the machine
and the Cassandra process crashes.

The weird thing is that this does not happen gradually 1 megabyte at a time. A server will
be more or less stable at around the same ram usage level for days and then suddenly grab
and hold 50-300mb extra ram within minutes and then stay at the new level. I have attached
two example of this.

The times this happens at seem random. They do not coincide with backups or repair jobs, for
one.

> Cassandra 3.10 crashes without dump
> -----------------------------------
>
>                 Key: CASSANDRA-13663
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13663
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Matthias Otto
>            Priority: Minor
>         Attachments: 2017-07-04 10_48_34-CloudWatch Management Console.png, cassandra
debug.log, cassandra system.log, RamUsageExamle1.png, RamUsageExample2.png
>
>
> Hello. My company runs a 5 node Cassandra cluster. For the last few weeks, we have had
a sporadic issue where one of the servers crashes without creating a dump file and without
any error messages in the logs. If one restarts the service (which we have by now scripted
to happen automatically), the servers resumes work with no complaint.
> Log files of the time of the last crash are attached, thou again they do not log any
crash happening.
> Regarding out setup, we are running these servers on AMazon AWS, with 3 volumes per server,
one for the system, one for data and one for the commitlog. When a crash happens, we can observe
a sudden spike of read activity on the commitlog volume. All of these have ample free space.
Aspecially the system volume has more then enough free space so that a dump could be written.
> The servers are Ubuntu 16.04 servers and Cassandra is installed from the apt-get packet
for version 3.10.
> It is worth noting that these crashes happen more often when nodetool is running either
repair job or a backup job, but this is by no means always the case. As for frequency, we
have had about 1-2 crashes per week for the last month.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message