Skip to content

Conversation

@Shawyeok
Copy link
Contributor

@Shawyeok Shawyeok commented Nov 7, 2025

Motivation

The configuration maxMessageSizeCheckIntervalInSeconds was introduced in #11141. After the topic local cache was added (#12830), this configuration became obsolete and is now unused.

Verifying this change

  • Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

  • Dependencies (add or upgrade a dependency)
  • The public API
  • The schema
  • The default values of configurations
  • The threading model
  • The binary protocol
  • The REST endpoints
  • The admin CLI options
  • The metrics
  • Anything that affects deployment

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

Matching PR in forked repository

PR in forked repository:

The configuration `maxMessageSizeCheckIntervalInSeconds` was introduced in apache#11141. After the topic local cache was added (apache#12830), this configuration became obsolete and is now unused.
@Shawyeok Shawyeok changed the title Remove unused configuration maxMessageSizeCheckIntervalInSeconds [fix][broker] Remove unused configuration maxMessageSizeCheckIntervalInSeconds Nov 7, 2025
@github-actions
Copy link

github-actions bot commented Nov 7, 2025

@Shawyeok Please add the following content to your PR description and select a checkbox:

- [ ] `doc` <!-- Your PR contains doc changes -->
- [ ] `doc-required` <!-- Your PR changes impact docs and you will update later -->
- [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
- [ ] `doc-complete` <!-- Docs have been already added -->

@github-actions github-actions bot added doc-not-needed Your PR changes do not impact docs and removed doc-label-missing labels Nov 7, 2025
@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.26%. Comparing base (186b503) to head (26ea9b1).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff              @@
##             master   #24958      +/-   ##
============================================
+ Coverage     74.21%   74.26%   +0.04%     
- Complexity    33905    33914       +9     
============================================
  Files          1913     1913              
  Lines        149510   149510              
  Branches      17373    17373              
============================================
+ Hits         110965   111039      +74     
+ Misses        29692    29639      -53     
+ Partials       8853     8832      -21     
Flag Coverage Δ
inttests 26.54% <ø> (?)
systests 22.72% <ø> (-0.01%) ⬇️
unittests 73.80% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 106 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@lhotari lhotari changed the title [fix][broker] Remove unused configuration maxMessageSizeCheckIntervalInSeconds [cleanup][broker] Remove unused configuration maxMessageSizeCheckIntervalInSeconds Nov 7, 2025
@lhotari lhotari merged commit d9a36b2 into apache:master Nov 7, 2025
57 of 61 checks passed
lhotari pushed a commit that referenced this pull request Nov 11, 2025
lhotari pushed a commit that referenced this pull request Nov 11, 2025
manas-ctds pushed a commit to datastax/pulsar that referenced this pull request Nov 13, 2025
…rvalInSeconds (apache#24958)

(cherry picked from commit d9a36b2)
(cherry picked from commit 3f00a00)
srinath-ctds pushed a commit to datastax/pulsar that referenced this pull request Nov 14, 2025
…rvalInSeconds (apache#24958)

(cherry picked from commit d9a36b2)
(cherry picked from commit 3f00a00)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants