[client] Add log read preference for remote-first fetch#3606
Open
zuston wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Purpose
The motivation of this PR is to reduce TabletServer RPC and local disk pressure when fetching high-throughput logs.
Based on observations from production workloads, when ingestion throughput reaches around 20 GB/s, log fetch traffic from the tiering service can reach about 30 GB/s. This puts significant additional pressure on TabletServers, especially on RPC handling and local disk reads.
link the issue of #3607
Brief change log
To address this, this PR makes it possible for tiering reads to fetch log data directly from remote storage when the requested offsets are already covered by remote logs.
Tests
API and Format
Documentation