Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add feature: enable maxSizePerLedger settings in configuration #7085

Merged

Conversation

wuzhanpeng
Copy link
Contributor

Motivation

This pull request implements an entrance to set max size per ledger in configuration file (conf/broker.conf). Currently the default ledger rollover size is hardcode to 2048MB when initializing broker in BrokerService.

Expected behaviors

If the user does not use the setting, the behaviors are the same as before. If the user sets managedLedgerMaxSizePerLedgerMbytes in conf/broker.conf, then the setting value will be used.

Modifications

  • two configuration files (conf/broker.conf and ServiceConfiguration)
  • one modification in initializing broker (BrokerService)

@@ -704,6 +704,9 @@ managedLedgerMinLedgerRolloverTimeMinutes=10
# Maximum time before forcing a ledger rollover for a topic
managedLedgerMaxLedgerRolloverTimeMinutes=240

# Maximum ledger size before triggering a rollover for a topic (MB)
managedLedgerMaxSizePerLedgerMbytes=2048
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also add this config into conf/standalone.conf?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your timely feedback. I have added the configuration in conf/standalone.conf.

@merlimat merlimat added the type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages label May 29, 2020
@merlimat merlimat added this to the 2.6.0 milestone May 29, 2020
@merlimat merlimat merged commit 0f5ffbf into apache:master May 31, 2020
Huanli-Meng pushed a commit to Huanli-Meng/pulsar that referenced this pull request Jun 1, 2020
…e#7085)

* add feature: enable maxSizePerLedger settings in configuration

* add feature: enable maxSizePerLedger settings in configuration

Co-authored-by: wuzhanpeng <wuzhanpeng@bigo.sg>
Huanli-Meng pushed a commit to Huanli-Meng/pulsar that referenced this pull request Jun 1, 2020
…e#7085)

* add feature: enable maxSizePerLedger settings in configuration

* add feature: enable maxSizePerLedger settings in configuration

Co-authored-by: wuzhanpeng <wuzhanpeng@bigo.sg>
Huanli-Meng pushed a commit to Huanli-Meng/pulsar that referenced this pull request Jun 12, 2020
…e#7085)

* add feature: enable maxSizePerLedger settings in configuration

* add feature: enable maxSizePerLedger settings in configuration

Co-authored-by: wuzhanpeng <wuzhanpeng@bigo.sg>
huangdx0726 pushed a commit to huangdx0726/pulsar that referenced this pull request Aug 24, 2020
…e#7085)

* add feature: enable maxSizePerLedger settings in configuration

* add feature: enable maxSizePerLedger settings in configuration

Co-authored-by: wuzhanpeng <wuzhanpeng@bigo.sg>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants