- Next hop feature for traffic server 8.0
Background and strategic fit
Traffic server Next generation of parent and origin selection
|1||Parent health status|
As of now Parent Status (UP/DOWN) is updated internally when a request to a parent results in a connection failure. ATS should be able to examine
& modify the status of Parent using a plugin interface & external mgmt interface.
|2||Health check plugin||Once we have the ability to update the parent status, there should be an example plugin to check the health of next hop and update the status.||Phasw 1|
3. delete the continuation for currently, health checked Next Hop if does not appear in the current list or if it manually marked down.
External health check process
|External process for health checking and updating the status of the Next Hop||Phase 1|
Requires management API to update hostb health record status (WIP).
|4||Self detection||Ability to detect the request that is going to end up on the same server and direct the request to next server.||Phase 1||Issue 2269, update parent selection findParent()|
|5||parent configuration in remap.config.||Add a new remap.config tag in remap.config, @parent, that may be used to configure next hop parents and the parent selection strategy.||Phase 2|
|6||Next Hop Match API.|
1) remap rules matching a given parent
2) Parents matching a given URL
Below is a list of questions to be addressed as a result of this requirements document: