Reduce maximum topic size to 50MB #2469
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Discussed this with @toddboom -- purely a default setting change, so merging on green. |
1GB per topic seems way to large. Instead make it 50MB. Topic data will never be deleted until at least 1 data node has replicated the data.
otoolep
force-pushed
the
reduce_min_topic_size
branch
from
5d0f8c5
to
8ed9e68
Compare
|
This value's definition isn't quite right yet, as tropic truncation still needs some work, but this should reduce current space requirements on brokers significantly. |
otoolep
added a commit
that referenced
this pull request
May 1, 2015
Reduce maximum topic size to 50MB
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
1GB per topic seems way too large. Instead make it 50MB. Topic data will
never be deleted until at least 1 data node has replicated the data, regardless of size.