You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to implement the health check and retry mechanism:
Use the upstream_id method in the plugin to refer to the defined upstream so that we can reuse the health detection and retry mechanism that the upstream already has.
Reasons for the init.lua file to adjust the execution order of plugins:
Since the upstream_id in the init.lua file is processed before the plugin is executed, it will cause the upstream_id setting in the traffic-split plugin to take effect. Therefore, this PR adjusts the logic code executed by the plug-in in the init.lua file before the processing of upstream_id.
Pre-submission checklist:
Did you explain what problem does this PR solve? Or what new features have been added?
Have you added corresponding test cases?
Have you modified the corresponding document?
Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first
Firstsawyou
changed the title
feat: the traffic-split plugin supports health check and retry mechanism
feat: the traffic-split plugin supports upstream_id
Feb 4, 2021
What is the relationship between this pr and #3094? I didn't see it
The feat of #3094 needs to be realized by supporting upstream_id in the plugin, and this pr is to solve the problem that the plugin supports upstream_id.
I still don't know why health check and retry mechanism are depends on upstream id?
Use the upstream_id method in the plugin to refer to the upstream that has been defined, so that we can reuse the health checks and retries that upstream already has, instead of repeatedly implementing them in the plugin.
I still don't know why health check and retry mechanism are depends on upstream id?
Use the upstream_id method in the plugin to refer to the upstream that has been defined, so that we can reuse the health checks and retries that upstream already has, instead of repeatedly implementing them in the plugin.
These should be explained in detail as much as possible in the issue and PR
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
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 this PR does / why we need it:
close #3094
How to implement the health check and retry mechanism:
Use the upstream_id method in the plugin to refer to the defined upstream so that we can reuse the health detection and retry mechanism that the upstream already has.
Reasons for the init.lua file to adjust the execution order of plugins:
Since the upstream_id in the init.lua file is processed before the plugin is executed, it will cause the upstream_id setting in the traffic-split plugin to take effect. Therefore, this
PRadjusts the logic code executed by the plug-in in the init.lua file before the processing ofupstream_id.Pre-submission checklist: