You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Apache9 (via GitHub)" <gi...@apache.org> on 2025/08/08 16:26:11 UTC
Re: [PR] HBASE-29463 Bidirectional serial replication will block if a region’s last edit before rs crashed was from the peer cluster [hbase]
Apache9 commented on PR #7172:
URL: https://github.com/apache/hbase/pull/7172#issuecomment-3168543042
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...
--
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: issues-unsubscribe@hbase.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org