[
https://issues.apache.org/jira/browse/TIKA-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas DiPiazza reassigned TIKA-5053:
---------------------------------------
Assignee: Nicholas DiPiazza
> tika-grpc: cancelled requests still use pipes clients
> -----------------------------------------------------
>
> Key: TIKA-5053
> URL: https://issues.apache.org/jira/browse/TIKA-5053
> Project: Tika
> Issue Type: Bug
> Components: tika-grpc, tika-pipes
> Affects Versions: 4.2.0
> Reporter: Davide Polato
> Assignee: Nicholas DiPiazza
> Priority: Major
> Attachments: CancelPropagationReproTest.java
>
>
> Following up on
> [TIKA-4795|https://issues.apache.org/jira/browse/TIKA-4795?focusedCommentId=18103818#comment-18103818].
> On main, cancelling a gRPC call or reaching its deadline does not stop its
> work. A cancelled request waiting for a pipes client can still start later.
> With numClients=1, running work holds up the next call until it finishes.
> [~tallison], would you handle cancellation below gRPC, including v1, or wait
> for the v2 decision on
> [TIKA-4766|https://issues.apache.org/jira/browse/TIKA-4766]? I have a
> prototype if useful.
> Attached: CancelPropagationReproTest.java (🤖 generated). It logs the sequence
> of events.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
