Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B3BDB10AEB for ; Sat, 20 Dec 2014 01:07:13 +0000 (UTC) Received: (qmail 87507 invoked by uid 500); 20 Dec 2014 01:07:13 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 87458 invoked by uid 500); 20 Dec 2014 01:07:13 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 87443 invoked by uid 99); 20 Dec 2014 01:07:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Dec 2014 01:07:13 +0000 Date: Sat, 20 Dec 2014 01:07:13 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-12733) High volume of "Couldn't find oldest seqNum" warnings if bypassing WAL MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Andrew Purtell created HBASE-12733: -------------------------------------- Summary: High volume of "Couldn't find oldest seqNum" warnings if bypassing WAL Key: HBASE-12733 URL: https://issues.apache.org/jira/browse/HBASE-12733 Project: HBase Issue Type: Bug Reporter: Andrew Purtell Priority: Minor When ingesting with the WAL bypassed, the RegionServer will log the following at every flush: {noformat} 2014-12-19 16:58:24,630 WARN [MemStoreFlusher.0] wal.FSHLog: Couldn't find oldest seqNum for the region we are about to flush: [86fc8c1374ebc29cc4a39a78966d48e0] {noformat} The WAL won't find a seqnum for the region until the first edit which does not bypass the WAL. That might not be for hundreds or thousands of flushes. This shouldn't be at WARN level since ingest with WAL bypass is legal if a bit unusual. It's concerning that the FSHLog code that emits that warning has a TODO above suggesting the warning should instead be an assertion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)