Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 22 May 2015 19:07:17 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12832028.1432262565000.12809.1432321637408@Atlassian.JIRA>
In-Reply-To: <JIRA.12832028.1432262565000@Atlassian.JIRA>
References: <JIRA.12832028.1432262565000@Atlassian.JIRA>
 <JIRA.12832028.1432262565760@arcas>
Subject: [jira] [Updated] (HBASE-13745) Say why a flush was requested in log
 message
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-13745:
--------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0
                   2.0.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Pushed to master and branch-1. Thanks for review [~srikanth235]

There is a zombie failure but no hanging tests apparently... need to dig in on this new type or fail mode.

> Say why a flush was requested in log message
> --------------------------------------------
>
>                 Key: HBASE-13745
>                 URL: https://issues.apache.org/jira/browse/HBASE-13745
>             Project: HBase
>          Issue Type: Improvement
>          Components: Operability
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
>             Fix For: 2.0.0, 1.2.0
>
>         Attachments: 13745.txt, 13745v2.txt, 13745v3.txt
>
>
> Looking at some logs that are full of flushes, we don't say why the flush request was made in the log message; would be helpful figuring if knew what was bringing on a flush in a particular context:
> Here is what it looks like:
> {code}
> 2095 2015-05-21 19:34:58,229 INFO  [localhost,51008,1432261786401_ChoreService_1] regionserver.HRegionServer: localhost,51008,1432261786401-MemstoreFlusherChore requesting flush of XXXX after random delay 15458ms
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)