cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-14474) Cassandra going down with `java.lang.OutOfMemoryError: Map failed`
Date Tue, 29 May 2018 17:45:00 GMT

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

Jeff Jirsa commented on CASSANDRA-14474:
----------------------------------------

This isn't a code bug, it's almost always incorrect user limits - check {{ulimit -a}} and
check the values of {{max memory size}} and {{virtual memory}} .



> Cassandra going down with `java.lang.OutOfMemoryError: Map failed`
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-14474
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14474
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: venky
>            Priority: Major
>
> From last couple of days, we are seeing this error in production and causing to down
the dse/cassandra. 
> DSE-5.1.2 & APACHE CASSANDRA-3.1.11
> ERROR [COMMIT-LOG-ALLOCATOR] 2018-05-29 04:16:33,582 JVMStabilityInspector.java:142 -
JVM state determined to be unstable. Exiting forcefully due to:
> java.lang.OutOfMemoryError: Map failed
> at sun.nio.ch.FileChannelImpl.map0(Native Method) ~[na:1.8.0_121]
> at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:937) ~[na:1.8.0_121]
> at org.apache.cassandra.db.commitlog.MemoryMappedSegment.createBuffer(MemoryMappedSegment.java:56)
~[cassandra-all-3.11.0.1758.jar:3.11.0.1758]
> at org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(CommitLogSegment.java:170)
~[cassandra-all-3.11.0.1758.jar:3.11.0.1758]
> at org.apache.cassandra.db.commitlog.MemoryMappedSegment.<init>(MemoryMappedSegment.java:45)
~[cassandra-all-3.11.0.1758.jar:3.11.0.1758]
> at org.apache.cassandra.db.commitlog.CommitLogSegment.createSegment(CommitLogSegment.java:124)
~[cassandra-all-3.11.0.1758.jar:3.11.0.1758]
> at org.apache.cassandra.db.commitlog.CommitLogSegmentManagerStandard.createSegment(CommitLogSegmentManagerStandard.java:78)
~[cassandra-all-3.11.0.1758.jar:3.11.0.1758]
> at org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager$1.runMayThrow(AbstractCommitLogSegmentManager.java:108)
~[cassandra-all-3.11.0.1758.jar:3.11.0.1758]
> at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28) [cassandra-all-3.11.0.1758.jar:3.11.0.1758]
> at org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81)
[cassandra-all-3.11.0.1758.jar:3.11.0.1758]
> at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_121]
> INFO [main] 2018-05-29 04:39:26,515 DseModule.java:90 - Loading DSE module
> INFO [main] 2018-05-29 04:39:26,734 YamlConfigurationLoader.java:89 - Configuration location:
file:/etc/dse/cassandra/cassandra.yaml
> INFO [main] 2018-05-29 04:39:27,039 DseConfigYamlLoader.java:38 - Loading settings from
file:/etc/dse/dse.yaml
> INFO [main] 2018-05-29 04:39:27,137 DseConfig.java:382 - Load of settings is done.
> INFO [main] 2018-05-29 04:39:27,138 YamlConfigurationLoader.java:89 - Configuration location:
file:/etc/dse/cassandra/cassandra.yaml



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message