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
Due to #1772 which introduced gRPC/HTTP multiplexing on the Executor. These changes mean that the Executor is created by the operator on port 8000 OR 5001 and all traffic (gRPC and HTTP) goes through one of those ports.
The executor used to be running on ports 8000 AND 5001. Thus the metrics example notebook looks for metrics on port 8000 in the gRPC example - when they are in fact running on port 5001.
This can be fixed by bringing the operator in line with the executor in regard to multiplexing.
https://github.com/SeldonIO/seldon-core/blob/master/examples/models/metrics/metrics.ipynb
... is broken.
Due to #1772 which introduced gRPC/HTTP multiplexing on the Executor. These changes mean that the Executor is created by the operator on port 8000 OR 5001 and all traffic (gRPC and HTTP) goes through one of those ports.
The executor used to be running on ports 8000 AND 5001. Thus the metrics example notebook looks for metrics on port 8000 in the gRPC example - when they are in fact running on port 5001.
This can be fixed by bringing the operator in line with the executor in regard to multiplexing.
Please see #1628
The text was updated successfully, but these errors were encountered: