Details
-
New Feature
-
Status: Closed
-
Minor
-
Resolution: Later
-
None
-
None
-
None
-
None
Description
We had a situation where we had massively overrun compactions during a load tests.
A single store ended up with something like 200 store files. This table also had large values, like 1MB+. A major compaction came in for the region and we OOME'd.
It would be useful to have a maximum number of files to include during a major compaction as a just-in-case measure if we do manage to get this many files in there. Can make it so 0 means infinite so there will be no change in default behavior.