[
https://issues.apache.org/jira/browse/HBASE-23157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950716#comment-16950716
]
Lijin Bin commented on HBASE-23157:
-----------------------------------
[~stack] We find a cluster with some regionserver have 20 thousand+ wals, and
hbase use is a internal version based on 1.2.5
{code}
2019-10-10 10:54:44,121 INFO [regionserver//9.46.144.197:60020.logRoller]
wal.FSHLog: Too many WALs; count=23446, max=96; forcing flush of 1 regions(s):
59802652fe21152f3eb9e73fdf4f2553
2019-10-10 10:54:44,121 WARN [regionserver//9.46.144.197:60020.logRoller]
regionserver.LogRoller: Failed to schedule flush of
59802652fe21152f3eb9e73fdf4f2553, region=null, requester=null
{code}
> WAL unflushed seqId tracking may wrong when Durability.ASYNC_WAL is used
> ------------------------------------------------------------------------
>
> Key: HBASE-23157
> URL: https://issues.apache.org/jira/browse/HBASE-23157
> Project: HBase
> Issue Type: Bug
> Components: regionserver, wal
> Affects Versions: 2.2.1
> Reporter: Lijin Bin
> Assignee: Lijin Bin
> Priority: Major
> Attachments: HBASE-23157-master-v1.patch
>
>
> Durability.ASYNC_WAL do not wait wal sync and commit mvcc ahead. So when
> region start flush may get a large flushedSeqId and later wal process buffer
> entry and put a small unflushedSequenceIds for this region again.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
