[
https://issues.apache.org/jira/browse/HBASE-23157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950717#comment-16950717
]
Lijin Bin commented on HBASE-23157:
-----------------------------------
[~zhangduo] this may cause regionserver have too many wals and also the WARN in
master also cause by it.
{code}
2019-10-07 21:09:49,101 WARN
[B.defaultRpcServer.handler=201,queue=21,port=60000] master.ServerManager:
RegionServer 9.46.144.221,60020,1565160409765 indicates a last flushed sequence
id (24529281) that is less than the previous last flushed sequence id
(24529341) for region
gdtdata_20191007,5680,1570302605714.187ad7634f6ca396fa2aab5cc5c83b61. Ignoring.
{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)
