Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7C35C200B51 for ; Mon, 18 Jul 2016 07:02:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7ADB7160A86; Mon, 18 Jul 2016 05:02:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C4CA4160A6B for ; Mon, 18 Jul 2016 07:02:21 +0200 (CEST) Received: (qmail 41894 invoked by uid 500); 18 Jul 2016 05:02:20 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 41865 invoked by uid 99); 18 Jul 2016 05:02:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jul 2016 05:02:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 721EB2C029F for ; Mon, 18 Jul 2016 05:02:20 +0000 (UTC) Date: Mon, 18 Jul 2016 05:02:20 +0000 (UTC) From: "Wei Deng (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-12221) Maximum Memory Usage Reached - NoSpamLogger MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 18 Jul 2016 05:02:22 -0000 [ https://issues.apache.org/jira/browse/CASSANDRA-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381723#comment-15381723 ] Wei Deng commented on CASSANDRA-12221: -------------------------------------- See CASSANDRA-5661. It's a cap to limit the amount of off-heap memory used by RandomAccessReader, and if there is a need, you can change the limit by file_cache_size_in_mb in cassandra.yaml. > Maximum Memory Usage Reached - NoSpamLogger > ------------------------------------------- > > Key: CASSANDRA-12221 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12221 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: CentOS 6.8 x86_64, Cassandra-3.0.7 > Reporter: vin01 > Priority: Minor > > I see some logs which look like :- > INFO [SharedPool-Worker-22] 2016-07-17 22:03:02,725 NoSpamLogger.java:91 - Maximum memory usage reached (536870912 bytes), cannot allocate chunk of 1048576 bytes > INFO [SharedPool-Worker-33] 2016-07-17 22:18:02,747 NoSpamLogger.java:91 - Maximum memory usage reached (536870912 bytes), cannot allocate chunk of 1048576 bytes > INFO [SharedPool-Worker-35] 2016-07-17 22:33:02,829 NoSpamLogger.java:91 - Maximum memory usage reached (536870912 bytes), cannot allocate chunk of 1048576 bytes > INFO [SharedPool-Worker-31] 2016-07-17 22:48:02,834 NoSpamLogger.java:91 - Maximum memory usage reached (536870912 bytes), cannot allocate chunk of 1048576 bytes > When i get these logs, CPU usage is quite high on the system. > Are they expected? Log message also seems confusing and i am not sure what memory we are talking about here.. -- This message was sent by Atlassian JIRA (v6.3.4#6332)