Skip to content

[LI-HOTFIX] Renaming the async fetcher classes to Async*#143

Merged
gitlw merged 1 commit into
linkedin:2.4-lifrom
gitlw:flag_async_fetcher_renaming
Apr 26, 2021
Merged

[LI-HOTFIX] Renaming the async fetcher classes to Async*#143
gitlw merged 1 commit into
linkedin:2.4-lifrom
gitlw:flag_async_fetcher_renaming

Conversation

@gitlw

@gitlw gitlw commented Apr 26, 2021

Copy link
Copy Markdown

TICKET = N/A
LI_DESCRIPTION =
I'd like to add a config to control whether the async fetcher threads feature should be enabled.
In order to do that, I'm using this PR to rename all the async fetcher classes by adding an Async prefix.

In a subsequent PR, I'll add the previous behavior back, including the classes for supporting lock-based fetcher threads.
EXIT_CRITERIA = N/A

Committer Checklist (excluded from commit message)

  • Verify design and implementation
  • Verify test coverage and CI build status
  • Verify documentation (including upgrade notes)

@gitlw gitlw requested a review from xiowu0 April 26, 2021 17:13
@gitlw gitlw merged commit 6a4efb9 into linkedin:2.4-li Apr 26, 2021
@gitlw gitlw deleted the flag_async_fetcher_renaming branch April 26, 2021 18:57
gitlw added a commit that referenced this pull request Feb 25, 2022
…ca fetcher threads (#143) (#144)

TICKET = N/A
LI_DESCRIPTION =
This PR adds a new config li.async.fetcher.enable to control whether the event-based fetcher threads should be used.
It chooses either the asyncReplicaFetcherManager or the replicaFetcherManager based on the new config li.async.fetcher.enable
EXIT_CRITERIA = N/A
lmr3796 pushed a commit to lmr3796/kafka that referenced this pull request Mar 25, 2022
…ca fetcher threads (linkedin#143) (linkedin#144)

TICKET = N/A
LI_DESCRIPTION =
This PR adds a new config li.async.fetcher.enable to control whether the event-based fetcher threads should be used.
It chooses either the asyncReplicaFetcherManager or the replicaFetcherManager based on the new config li.async.fetcher.enable
EXIT_CRITERIA = N/A
lmr3796 pushed a commit to lmr3796/kafka that referenced this pull request Jun 2, 2022
…fetcher threads (linkedin#143) (linkedin#144)

TICKET = N/A
LI_DESCRIPTION =
This PR adds a new config li.async.fetcher.enable to control whether the event-based fetcher threads should be used.
It chooses either the asyncReplicaFetcherManager or the replicaFetcherManager based on the new config li.async.fetcher.enable
EXIT_CRITERIA = N/A
earlcoder added a commit that referenced this pull request Apr 28, 2026
The async/event-based replica fetcher series (TransferLeaderManager,
AbstractAsyncFetcher, AsyncReplicaFetcher, FetcherEventBus,
FetcherEventManager — PRs #121/#123/#124/#143/#144/#403/#406) was
removed in the PR #538 squash. The li.async.fetcher.enable config key
was left behind in KafkaConfig as dead surface area: it parsed and
validated, but had no consumers.

Going with audit P1 #6 option (a): retire the feature, remove the dead
config key. Operators with li.async.fetcher.enable=<anything> in their
server.properties may see an 'Unknown configuration' warning at broker
startup; this is harmless — the broker still starts and the value would
have been a no-op anyway.

Removes:
- Defaults.LiAsyncFetcherEnabled
- KafkaConfig.LiAsyncFetcherEnableProp
- The brokerConfigDef.define(...) registration
- KafkaConfig.liAsyncFetcherEnable accessor

Audit option (b) — porting the entire async fetcher series forward
into 3.6-li — was deferred. If the optimization is needed in the
future, it would need to be reimplemented from scratch on top of
upstream's current ReplicaFetcherThread / ReplicaFetcherManager.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants