Andrew Kryczka f9d18e22d2 Fix DeleteRange file boundary correctness issue with max_compaction_bytes
Summary:
Cockroachdb exposed this bug in #1778. The bug happens when a compaction's output files are ended due to exceeding max_compaction_bytes. In that case we weren't taking into account the next file's start key when deciding how far to extend the current file's max_key. This caused the non-overlapping key-range invariant to be violated.

Note this was correctly handled for the usual case of cutting compaction output, which is file size exceeding max_output_file_size. I am not sure why these are two separate code paths, but we can consider refactoring it to prevent such errors in the future.
Closes https://github.com/facebook/rocksdb/pull/1784

Differential Revision: D4430235

Pulled By: ajkr

fbshipit-source-id: 80af748
2017-01-18 11:54:22 -08:00
..
2016-11-21 12:24:13 -08:00
2016-11-19 14:24:12 -08:00
2017-01-03 18:39:14 -08:00
2017-01-03 18:39:14 -08:00
2016-11-23 09:24:15 -08:00
2017-01-08 14:24:12 -08:00
2017-01-08 14:24:12 -08:00
2017-01-08 14:24:12 -08:00
2017-01-08 14:24:12 -08:00
2017-01-08 14:24:12 -08:00
2016-11-04 12:09:22 -07:00
2016-12-19 14:09:12 -08:00
2017-01-17 13:54:20 -08:00
2017-01-03 17:54:12 -08:00
2017-01-09 15:54:12 -08:00
2016-11-10 11:09:22 -08:00
2016-12-19 16:54:12 -08:00
2016-07-08 17:50:51 -07:00
2016-10-13 08:48:40 -07:00
2016-07-08 17:50:51 -07:00
2016-11-03 18:54:20 -07:00
2017-01-08 14:24:12 -08:00
2017-01-08 14:24:12 -08:00
2017-01-08 14:24:12 -08:00
2017-01-08 14:24:12 -08:00
2016-12-29 15:54:19 -08:00
2016-11-19 14:24:12 -08:00
2016-09-27 18:20:57 -07:00
2016-09-27 18:20:57 -07:00
2016-07-13 15:36:22 -07:00
2017-01-08 14:24:12 -08:00
2017-01-08 14:24:12 -08:00
2016-11-21 18:09:13 -08:00