[
https://issues.apache.org/jira/browse/IGNITE-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330074#comment-17330074
]
Alexand Polyakov commented on IGNITE-9386:
------------------------------------------
relevant for master (2021.04.23)
> control.sh --tx can produce confusing results when limit is set to small value
> ------------------------------------------------------------------------------
>
> Key: IGNITE-9386
> URL: https://issues.apache.org/jira/browse/IGNITE-9386
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh
> Reporter: Alexey Scherbakov
> Priority: Major
>
> This is happening because currently the limit is applied to primary and
> backup transactions, which breaks output post-filtering (removal of primary
> and backup transactions from output if near is present).
> Possible solution: apply limit only to near valid transactions. If some txs
> have no near part (broken tx topology), they should be always visible in
> output, probably with special "broken" marking.
> Best way to achieve this - implement tx paging on client side (using
> continuous mapping)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
