[
https://issues.apache.org/jira/browse/IGNITE-16719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511425#comment-17511425
]
Konstantin Orlov commented on IGNITE-16719:
-------------------------------------------
[~alapin] , LGTM!
> Inconsistent counters exception in case of
> subscription.request(Long.MAX_VALUE);
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-16719
> URL: https://issues.apache.org/jira/browse/IGNITE-16719
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexander Lapin
> Assignee: Alexander Lapin
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Attachments:
> bugreport-blackjack-QODS30.163-7-27-2022-03-13-13-48-43-dumpstate_log-17151.txt
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In case of requesting an amount of rows that is much bigger than
> internalBatchSize using
> {code:java}
> InternalTableImpl.PartitionScanPublisher.PartitionScanSubscription#request{code}
> it's possible to hang up or get an IllegalStateException("Counters from
> received scan command and handled scan command in partition listener are
> inconsistent")
> Seems that the reason of such behavior is in eager creation of scan requests
> on the client size. Ordering the creation of next scan request with
> processing the response of the previous one should eliminate given problem.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
