Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 26AB3C742 for ; Thu, 24 May 2012 14:22:57 +0000 (UTC) Received: (qmail 58378 invoked by uid 500); 24 May 2012 14:22:56 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 58121 invoked by uid 500); 24 May 2012 14:22:56 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 57709 invoked by uid 99); 24 May 2012 14:22:56 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 May 2012 14:22:56 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 09B7014281C for ; Thu, 24 May 2012 14:22:56 +0000 (UTC) Date: Thu, 24 May 2012 14:22:56 +0000 (UTC) From: "John Vines (JIRA)" To: dev@accumulo.apache.org Message-ID: <841753907.274.1337869376042.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Created] (ACCUMULO-604) Running Low On Memory messages in monitor is a bit overzealous MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 John Vines created ACCUMULO-604: ----------------------------------- Summary: Running Low On Memory messages in monitor is a bit overzealous Key: ACCUMULO-604 URL: https://issues.apache.org/jira/browse/ACCUMULO-604 Project: Accumulo Issue Type: Bug Components: monitor Affects Versions: 1.5.0-SNAPSHOT Reporter: John Vines Assignee: John Vines Fix For: 1.5.0 Ran the functional tests overnight and I came in to find that one of the multi-server tests had not cleaned up. The monitor logs had rolled multiple times. First of all, it was logging so much that events were being logged out of order. I saw "[tabletserver.TabletServer] WARN : Running low on memory" as the reoccuring message, spamming the logs every 5-30 seconds, with a smidge over 7000 entries per time period. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira