You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by GitBox <gi...@apache.org> on 2022/03/12 16:24:52 UTC

[GitHub] [hbase] joshelser commented on pull request #4202: HBASE-26791 Memstore flush fencing issue for SFT

joshelser commented on pull request #4202:
URL: https://github.com/apache/hbase/pull/4202#issuecomment-1065912257


   > Bump the timestamp/sequenceid, to a value greater than the loaded timestamp/sequenceid, and we will use this timestamp/sequenceid as new track file names.
   In this way, the old rs will only overwrite the track files with old timestamp/sequenceid, so it will not effect the new track files. So the problem can be solved.
   
   Ah, so is it that we use the sequenceId _only_ when opening the Region (store). After the region is open, choosing whether to use f1 or f2 is then based on what `getTimestamp()` returns for those two files? That makes more sense.
   
   Sorry I missed your explanation on Jira.


-- 
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