KFServing component missing request timeout support
See original GitHub issue/kind bug /kind feature
Hi. Recently the KFServing component for the pipeline was updated to v0.5.1 supporting v1beta1 API. This component is still missing the timeout
field in PredictorSpec which specifies the number of seconds to wait before timing out a request to the component. A couple of issues were raised in this regard:
I would be happy to submit a PR as seems like a very small change. ❤️
Proposed solution:
Add an extra args named requestTimeout
to component yaml and use this as parameter in the create_predictor_spec
function.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Issues and Workarounds
1, the Kubernetes Dashboard becomes inaccessable and returns an error 503 Service Unavailable . This issue was fixed in HPE Ezmeral Runtime Enterprise...
Read more >KServe | Kubeflow
Highly scalable and standards based Model Inference Platform on Kubernetes for Trusted AI.
Read more >docs/apis/v1beta1/README.md · garlong/kubeflow-kfserving
ComponentType contains the different types of components of the service ... Default timeout of predictor for serving a request, in seconds.
Read more >Changelog — seldon-core documentation
Python request logger example component deprication and removal ``#4016` ... Support kfserving protocol in status URL ``#3064` ...
Read more >Changelog — Rok 1.5.3 documentation
Fix CSI etcd Job handling code to decrease the timeout in case of stale revision ... Restore support for the KFServing PMML predictor...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@midhun1998 You can go ahead and submit a PR as it can always be rebased, and I don’t foresee any conflicts. I will build and push the image with your changes once it passes the review process.
Hi @Bobgy. I will be opening a PR soon. I have added it and I’m currently testing.