You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "erikseulean (via GitHub)" <gi...@apache.org> on 2024/04/04 04:23:44 UTC
[I] Can you provide best practices around cancellations [arrow]
erikseulean opened a new issue, #40993:
URL: https://github.com/apache/arrow/issues/40993
### Describe the usage question you have. Please include as many useful details as possible.
I have an ArrowFlight service handling requests. In normal working conditions everything works fine. I'd like to be able to setup timeouts on long running requests.
Currently the client has an option for a timeout but what happens if the timeout is reached ? From some debugging it feels like the service never gets communicated that the client has timed out, therefore it can continue running an expensive query.
I can have a server side and a client side timeout but this is not necessarily ideal. The server side timeout is hard to manage properly.
My question here is - what is the best practice/how to cancel a request such that the handling service is stopped from performing whatever action it is performing if the client is not waiting for the answer anymore ?
### Component(s)
FlightRPC, Python
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Can you provide best practices around cancellations [arrow]
Posted by "lidavidm (via GitHub)" <gi...@apache.org>.
lidavidm commented on issue #40993:
URL: https://github.com/apache/arrow/issues/40993#issuecomment-2036167366
context.is_cancelled() _should_ propagate this but if not, then something is up with gRPC (we are just wrapping what gRPC provides)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Python][FlightRPC] Can you provide best practices around cancellations [arrow]
Posted by "thisisnic (via GitHub)" <gi...@apache.org>.
thisisnic commented on issue #40993:
URL: https://github.com/apache/arrow/issues/40993#issuecomment-3547491978
This issue has been marked as stale because it has had no activity in the past 365 days. Please remove the stale label or comment below, or this issue will be closed in 14 days. If this usage question has evolved into a feature request or docs update, please remove the 'Type: usage' label and add the 'Type: enhancement' label instead.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Python][FlightRPC] Can you provide best practices around cancellations [arrow]
Posted by "thisisnic (via GitHub)" <gi...@apache.org>.
thisisnic closed issue #40993: [Python][FlightRPC] Can you provide best practices around cancellations
URL: https://github.com/apache/arrow/issues/40993
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org