You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/05/26 22:30:13 UTC

[jira] [Resolved] (HBASE-12733) High volume of "Couldn't find oldest seqNum" warnings if bypassing WAL

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

stack resolved HBASE-12733.
---------------------------
    Resolution: Won't Fix

Resolving won't fix. Old issue in a location that has undergone a bunch of refactoring since original filed. If someone has later evidence, lets reopen.

> 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
>              Labels: beginner
>
> 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)