Cancellation of HTTP triggers waiting for python language workers does not work
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
Check for a solution in the Azure portal
For issues in production, please check for a solution to common issues in the Azure portal before opening a bug. In the Azure portal, navigate to your function app, select Diagnose and solve problems from the left, and view relevant dashboards before opening your issue.
Investigative information
Please provide the following:
- Timestamp: 2021-11-08T16:46:57.915Z
- Function App version: mcr.microsoft.com/azure-functions/python:3.0-python3.8-appservice
- Function App name:
- Function name(s) (as appropriate):
- Invocation ID: fa416bc3-f801-45db-939a-2145fcef7bee
- Region: West Europe
Repro steps
Provide the steps required to reproduce the problem:
- Create a function app with 2 functions
- trigger function 1 that will have a long IO operation and will take the language worker
- trigger function 2 which is a HTTP one multiple times and cancel requests before they are handled by language worker
Expected behavior
Provide a description of the expected behavior.
HTTP-triggered Function invocations waiting for language worker should not be processed if client closed the request while function is waiting in queue.
Actual behavior
Provide a description of the actual behavior observed.
HTTP function executes long after client gave up waiting and closed the connection.
Known workarounds
Provide a description of any known workarounds.
In C# we can get a cancellation token from request context. but here the request sits in function host and arrives to python worker afer seconds or minutes. No workaround known.
Related information
Provide any related information
- Programming language used: Python
- Links to source: n/a
- Bindings used: none, HTTP trigger
- Dominant language
- Python
- Stars
- 357
- Forks
- 116
- Avg merge
- 32m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/azure-functions-python-worker
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug python
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Azure/azure-functions-python-worker#1881 · 2 comments · 3 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
Azure/azure-functions-python-worker#1908 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Azure/azure-functions-python-worker#1906 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in Azure/azure-functions-python-worker
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100