[
https://issues.apache.org/jira/browse/IGNITE-23299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-23299:
-----------------------------------------
Labels: ignite-3 (was: ignite3)
> 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: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
