[
https://issues.apache.org/jira/browse/HBASE-25541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285430#comment-17285430
]
Bharath Vissapragada commented on HBASE-25541:
----------------------------------------------
[~anoop.hbase] I believe the issue is this. If `openNextLog()` throws (in
openReader() for whatever reason), currentPath would be pointing to the last
dequeued log. From that point on the logs are misleading (especially if the
queue processing is stuck at that point).
{noformat}
private boolean openNextLog() throws IOException {
Path nextPath = logQueue.peek();
if (nextPath != null) {
openReader(nextPath); <===
if (reader != null) {
return true;
}
} else {
// no more files in queue, this could happen for recovered queue, or for a
wal group of a sync
// replication peer which has already been transited to DA or S.
setCurrentPath(null);
}
return false;
} {noformat}
[~sandeep.pal] Correct me if I'm wrong
> In WALEntryStream, set the current path to null while dequeing the log
> ----------------------------------------------------------------------
>
> Key: HBASE-25541
> URL: https://issues.apache.org/jira/browse/HBASE-25541
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 1.6.0, 1.7.0, 1.8.0
> Reporter: Sandeep Pal
> Assignee: Sandeep Pal
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
