1. 01 11月, 2016 6 次提交
  2. 30 10月, 2016 3 次提交
  3. 29 10月, 2016 10 次提交
  4. 28 10月, 2016 1 次提交
  5. 26 10月, 2016 2 次提交
    • K
      Makefile: generate util/build_version.cc from .in file (#1384) · 60a2bbba
      Kefu Chai 提交于
      * util/build_verion.cc.in: add this file, so cmake and make can share the
        template file for generating util/build_version.cc.
      * CMakeLists.txt: also, cmake v2.8.11 does not support file(GENERATE ...),
        so we are using configure_file() for creating build_version.cc.
      * Makefile: use util/build_verion.cc.in for creating build_version.cc.
      Signed-off-by: NKefu Chai <tchaikov@gmail.com>
      60a2bbba
    • S
      Disable DBTest.RepeatedWritesToSameKey (#1420) · 9ee84067
      Siying Dong 提交于
      Summary:
      The verification condition of the test DBTest.RepeatedWritesToSameKey doesn't hold anymore after 3ce3bb3d.
      Disable the test for now before we find a way to replace it.
      
      Test Plan: Run the test and make sure it is disabled.
      9ee84067
  6. 25 10月, 2016 5 次提交
    • S
      OptionChangeMigration() to support FIFO compaction · f41df304
      sdong 提交于
      Summary: OptionChangeMigration() to support FIFO compaction. If the DB before migration is using FIFO compaction, nothing should be done. If the desitnation option is FIFO options, compact to one single L0 file if the source has more than one levels.
      
      Test Plan: Run option_change_migration_test
      
      Reviewers: andrewkr, IslamAbdelRahman
      
      Reviewed By: IslamAbdelRahman
      
      Subscribers: leveldb, andrewkr, dhruba
      
      Differential Revision: https://reviews.facebook.net/D65289
      f41df304
    • A
      Changing the legocastle run to use valgrind_test instead of _check · 2e8004e6
      Anirban Rahut 提交于
      Summary:
      valgrind_test is the correct way to run valgrind tests.
      this is becasue we need to force DISABLE_JEMALLOC
      
      Test Plan: Running sandcastle and contrun
      
      Reviewers: IslamAbdelRahman
      
      Reviewed By: IslamAbdelRahman
      
      Subscribers: andrewkr, dhruba
      
      Differential Revision: https://reviews.facebook.net/D65451
      2e8004e6
    • A
      revert Prev() in MergingIterator to use previous code in non-prefix-seek mode · 9de2f752
      Aaron Gao 提交于
      Summary: Siying suggested to keep old code for normal mode prev() for safety
      
      Test Plan: make check -j64
      
      Reviewers: yiwu, andrewkr, sdong
      
      Reviewed By: sdong
      
      Subscribers: andrewkr, dhruba, leveldb
      
      Differential Revision: https://reviews.facebook.net/D65439
      9de2f752
    • S
      DBSSTTest.RateLimitedDelete: not to use real clock · 24495186
      sdong 提交于
      Summary: Using real clock causes failures of DBSSTTest.RateLimitedDelete in some cases. Turn away from the real time. Use fake time instead.
      
      Test Plan: Run the tests and all existing tests.
      
      Reviewers: yiwu, IslamAbdelRahman
      
      Reviewed By: IslamAbdelRahman
      
      Subscribers: leveldb, andrewkr, dhruba
      
      Differential Revision: https://reviews.facebook.net/D65145
      24495186
    • S
      Fix a bug that may cause a deleted row to appear again · 1168cb81
      sdong 提交于
      Summary:
      The previous fix of reappearing of a deleted row 0ce258f9 missed a corner case, which can be reproduced using test CompactionPickerTest.OverlappingUserKeys7. Consider such an example:
      
      input level file: 1[B E] 2[F H]
      output level file: 3[A C] 4[D I] 5[I K]
      
      First file 2 is picked, which overlaps to file 4. 4 expands to 5. Now the all range is [D K] with 2 output level files. When we try to expand that, [D K] overlaps with file 1 and 2 in the input level, and 1 and 2 overlaps with 3 and 4 in the output level. So we end up with picking 3 and 4 in the output level. Without expanding, it also has 2 files, so we determine the output level doesn't change, although they are the different two files.
      
      The fix is to expand the output level files after we picked 3 and 4. In that case, there will be three output level files so we will abort the expanding.
      
      I also added two unit tests related to marked_for_compaction and being_compacted. They have been passing though.
      
      Test Plan: Run the new unit test, as well as all other tests.
      
      Reviewers: andrewkr, IslamAbdelRahman
      
      Reviewed By: IslamAbdelRahman
      
      Subscribers: yoshinorim, leveldb, andrewkr, dhruba
      
      Differential Revision: https://reviews.facebook.net/D65373
      1168cb81
  7. 24 10月, 2016 1 次提交
  8. 22 10月, 2016 4 次提交
  9. 21 10月, 2016 2 次提交
    • I
      Support IngestExternalFile (remove AddFile restrictions) · 869ae5d7
      Islam AbdelRahman 提交于
      Summary:
      Changes in the diff
      
      API changes:
      - Introduce IngestExternalFile to replace AddFile (I think this make the API more clear)
      - Introduce IngestExternalFileOptions (This struct will encapsulate the options for ingesting the external file)
      - Deprecate AddFile() API
      
      Logic changes:
      - If our file overlap with the memtable we will flush the memtable
      - We will find the first level in the LSM tree that our file key range overlap with the keys in it
      - We will find the lowest level in the LSM tree above the the level we found in step 2 that our file can fit in and ingest our file in it
      - We will assign a global sequence number to our new file
      - Remove AddFile restrictions by using global sequence numbers
      
      Other changes:
      - Refactor all AddFile logic to be encapsulated in ExternalSstFileIngestionJob
      
      Test Plan:
      unit tests (still need to add more)
      addfile_stress (https://reviews.facebook.net/D65037)
      
      Reviewers: yiwu, andrewkr, lightmark, yhchiang, sdong
      
      Reviewed By: sdong
      
      Subscribers: jkedgar, hcz, andrewkr, dhruba
      
      Differential Revision: https://reviews.facebook.net/D65061
      869ae5d7
    • S
      Restrict running condition of UniversalCompactionTrivialMoveTest2 · 1d9dbef6
      sdong 提交于
      Summary: DBTestUniversalCompaction.UniversalCompactionTrivialMoveTest2 verifies non-trivial move is not triggered if we load data in sequential order. However, if there are multiple compaction threads, this conditon may not hold. Restrict the running condition to 1 compaction thread to make the test more robust.
      
      Test Plan: Run the test and make sure at least it doesn't regress normally.
      
      Reviewers: yhchiang, andrewkr, IslamAbdelRahman
      
      Reviewed By: IslamAbdelRahman
      
      Subscribers: leveldb, andrewkr, dhruba
      
      Differential Revision: https://reviews.facebook.net/D65277
      1d9dbef6
  10. 20 10月, 2016 6 次提交