feat: RandomStrategy AliveOnly #2850
Merged
+241
−125
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.
Address #1841.
New optional settings to strategy
random
:aliveOnly
andobserverTag
.If
aliveOnly == true
, enable the strategy to choose only from alive outbounds. Outbounds are considered alive unless proven otherwise (by observatory).Very useful when one has several unstable outbounds, this improves reliability by making these outbounds fail-safe to each other.
Also useful when one wants to combine bandwidth of several unstable outbounds.
Use like
Need
observatory
.FAQ
Fully compatible with the original
random
strategy, i.e. no strategy at all.It adds a check upon picking an outbound, i.e. whether ones has a
random strategy
. Almost no performance effect.obsolete
New balancer strategy: `randomalive`.Random, but only choose from alive outbounds.
Use like