Apache9 commented on PR #7172: URL: https://github.com/apache/hbase/pull/7172#issuecomment-3169917170
> OK, there are still some problems... > > Seems we still need to know why an entry is skipped then we can determine whther we should update the last pushed sequence id. For example, when sending wal entries for a new range, the first wal is opening marker, we will always filter it out because it does not have a replication scope. In this case, if we just treat it as 'can push', then we will update the last pushed sequence id even if the previous range is not finished. > > Let me think how to deal with this scenario... So the solution is go back to the old way, tell the filter we are serial replication peer, so the filter should not return null as we still need to wal entry for recording progress. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
