Add secor.max.active.files property to controll active file count #1443
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Partially addresses #785
Keeps active file under
secor.max.file.count
(default 100)@HenryCaiHaiying , what do you think, is this the right way to approach this problem? I was thinking, maybe Files should be sorted by size before calling
checkTopicPartition
so that the biggest file is uploaded first, but decided to keep that simple for now.Tried it for our use case (big number of partitions in small amount of time) it helped with OutOfMemory exception.