• A
    Do not allow Transaction Log Iterator to fall ahead when writer is writing the same file · d68880a1
    Abhishek Kona 提交于
    Summary:
    Store the last flushed, seq no. in db_impl. Check against it in
    transaction Log iterator. Do not attempt to read ahead if we do not know
    if the data is flushed completely.
    Does not work if flush is disabled. Any ideas on fixing that?
    * Minor change, iter->Next is called the first time automatically for
    * the first time.
    
    Test Plan:
    existing test pass.
    More ideas on testing this?
    Planning to run some stress test.
    
    Reviewers: dhruba, heyongqiang
    
    CC: leveldb
    
    Differential Revision: https://reviews.facebook.net/D9087
    d68880a1
db_test.cc 91.2 KB