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.
What type of PR is this:
Which issues of this PR fixes :
Fixes #
Problem Summary(Required) :
Usage Note for StarRocks BE Host Mapping Configuration on Kubernetes
Overview:
When running Starrocks on Kubernetes environments, the internal service names of StarRocks backend (BE) nodes might differ from their corresponding external IPs or domain names. To facilitate seamless connectivity, we support configuring a mapping between these internal service names and their external counterparts using the
starrocks.be.host.mapping.list
configuration.Configuration:
The
starrocks.be.host.mapping.list
property allows users to specify a list of mappings between the external IPs or domain names and internal service names of StarRocks BE nodes.Format:
Example:
For instance, suppose the following mappings are required:
20.11.12.13:9060
maps to internal service namestarrocks-cdc-cn-0.starrocks-cdc-cn-search.starrocks.svc.cluster.local:9060
.21.11.12.13:9060
maps to internal service namestarrocks-cdc-cn-1.starrocks-cdc-cn-search.starrocks.svc.cluster.local:9060
.You can specify these mappings as:
Checklist: