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

Fix Bug Where Weight Is Set to 0 in Ramping-Up Strategy #6014

Merged
merged 8 commits into from
Dec 3, 2024

Conversation

minwoox
Copy link
Contributor

@minwoox minwoox commented Dec 3, 2024

Motivation:
When the original weight is less than 10, the initial weight is incorrectly set to 0, potentially leading to EndpointSelectionTimeoutException.

Modifications:

  • Ensured a minimum weight of 1 is set when the original weight is greater than 1 in the ramping-up strategy.
  • Added debugging logs for selector and selection strategy to facilitate troubleshooting.

Result:

  • Fix a bug where weights could unintentionally be set to 0 in ramping-up strategies.

Motivation:
The remoteAddress metric can be useful for CSLB clients.
However, including this metric could significantly increase the cardinality of metrics when dealing with numerous endpoints.
To address this, we should offer an opt-in mechanism.

Modifications:
- Introduced `MeterIdPrefixFunction.builderForClient()` to enable users to manage metric tags:
  - Users can specify tags to include or exclude using `includeTags` and `excludeTags` in the `ClientMeterIdPrefixFunctionBuilder`.
- Added debugging logs for selector and selection strategy to aid in troubleshooting.

Result:
- You can now optionally include the `remoteAddress` metric.
Motivation:
When the original weight is less than 10, the initial weight is incorrectly set to 0, potentially leading to `EndpointSelectionTimeoutException`.

Modifications:
- Ensured a minimum weight of 1 is set when the original weight is greater than 1 in the ramping-up strategy.
- Added debugging logs for selector and selection strategy to facilitate troubleshooting.

Result:
- Fix a bug where weights could unintentionally be set to 0 in ramping-up strategies.
@minwoox minwoox added the defect label Dec 3, 2024
@minwoox minwoox added this to the 1.31.2 milestone Dec 3, 2024
Copy link
Member

@trustin trustin left a comment

Choose a reason for hiding this comment

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

🙇

@minwoox minwoox merged commit 62da203 into line:main Dec 3, 2024
12 of 14 checks passed
@minwoox minwoox deleted the more_logs2 branch December 3, 2024 12:03
minwoox added a commit that referenced this pull request Dec 3, 2024
Motivation:
When the original weight is less than 10, the initial weight is incorrectly set to 0, potentially leading to `EndpointSelectionTimeoutException`.

Modifications:
- Ensured a minimum weight of 1 is set when the original weight is greater than 1 in the ramping-up strategy.
- Added debugging logs for selector and selection strategy to facilitate troubleshooting.

Result:
- Fix a bug where weights could unintentionally be set to 0 in ramping-up strategies.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants