You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2024/09/27 08:11:00 UTC

[jira] [Assigned] (IGNITE-23299) Sql. Fix invalid inflight transaction tracking.

     [ https://issues.apache.org/jira/browse/IGNITE-23299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Mashenkov reassigned IGNITE-23299:
-----------------------------------------

    Assignee: Andrey Mashenkov

> Sql. Fix invalid inflight transaction tracking.
> -----------------------------------------------
>
>                 Key: IGNITE-23299
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23299
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Andrey Mashenkov
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite3
>
> PartitionScanSubscription may unexpectedly trigger `inflightBatchRequestTracker.onRequestEnd()` twice in case of batch processing error. in `scanBatch` method.
> The first call is expected and happens on happy-path after getting a successful response.
> But if batch processing failed with error (e.g. `subscriber::onNext`), then we get into unhappy-path and trigger `inflightBatchRequestTracker.onRequestEnd()` once again, which violates the contract.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)