From 65d487f2255655741018a3ff04ac08671012abcf Mon Sep 17 00:00:00 2001 From: Clive Cox Date: Mon, 20 Jul 2020 18:35:44 +0100 Subject: [PATCH] Routing disclaimer in executor --- doc/source/analytics/routers.md | 4 ++++ doc/source/graph/svcorch.md | 6 +++++- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/source/analytics/routers.md b/doc/source/analytics/routers.md index 7bfaf039e5..03c815e1ab 100644 --- a/doc/source/analytics/routers.md +++ b/doc/source/analytics/routers.md @@ -16,3 +16,7 @@ As an example, consider writing a custom A/B/C... testing component with a user- Because routers are generic components that only need to implement the ```Route``` method, there is considerable flexibility in designing the routing logic. Some example concepts going beyond random testing and multi-armed bandits: * Routing depending on external conditions, e.g. use the time of day to route traffic to a model that has been known to perform best during a particular time period. * Model as a router: use a predictive model within a router component to first determine a higher level class membership (e.g. cat vs dog) and according to the decision route traffic to more specific models (e.g. dog-specific model to infer a breed). + +## Limitations + +The current default orchestrator in Go the "executor" does not return routing meta data in request calls. This is a [known issue](https://github.com/SeldonIO/seldon-core/issues/1823). \ No newline at end of file diff --git a/doc/source/graph/svcorch.md b/doc/source/graph/svcorch.md index 0014752ee4..f28b556514 100644 --- a/doc/source/graph/svcorch.md +++ b/doc/source/graph/svcorch.md @@ -129,7 +129,7 @@ You can set custom resource request and limits for this component by specifying ``` -## Bypass Service Orchestrator (version >= 0.5.0, alpha feature) +## Bypass Service Orchestrator (version >= 0.5.0) If you are deploying a single model then for those wishing to minimize the latency and resource usage for their deployed model you can opt out of having the service orchestrator included. To do this add the annotation `seldon.io/no-engine: "true"` to the predictor. The predictor must contain just a single node graph. An example is shown below: @@ -163,3 +163,7 @@ spec: In these cases the external API requests will be sent directly to your model. At present only the python wrapper (>=0.13-SNAPSHOT) has been modified to allow this. Note no metrics or extra data will be added to the request so this would need to be done by your model itself if needed. + +## Routing in Metadata + +The current default orchestrator in Go the "executor" does not return routing meta data in request calls. This is a [known issue](https://github.com/SeldonIO/seldon-core/issues/1823). \ No newline at end of file