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

Parent selection secondary_mode config value 3 is not working as documented #6847

Closed
Vijay-1 opened this issue Jun 3, 2020 · 3 comments
Closed
Assignees

Comments

@Vijay-1
Copy link
Contributor

Vijay-1 commented Jun 3, 2020

secondary_mode -3
scenario #1
Expectation
If the chosen parent is marked down then another parent will be chosen from the secondary_parent list. The secondary_parent list will be exhausted before attempting to choose another parent in the parent list.

Behaviour
Chosen parent is marked down. The remaining parent in the primary list is getting chosen instead of trying parents from secondary_list

parent.config

dest_ip=10.x.x.x port=80 parent="ts-mid3.testing.in:80|0.1;ts-mid4.testing.in:80|0.1;" secondary_parent="ts-mid1.testing.in:80|0.1;ts-mid2.testing.in:80|0.1;" round_robin=consistent_hash go_direct=false qstring=ignore secondary_mode=3

@Vijay-1
Copy link
Contributor Author

Vijay-1 commented Jun 4, 2020

This is not an issue. One has to take parents down using traffic_ctl host down for this to work as documented. PR-Documentation-fix

@jrushford jrushford self-assigned this Jul 23, 2020
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. Marking it stale to flag it for further consideration by the community.

@github-actions github-actions bot added the Stale label Jul 24, 2021
@bryancall
Copy link
Contributor

Looks like this has been fixed. Please reopen if there is still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants