[jira] [Updated] (IGNITE-9386) control.sh --tx can produce confusing results when limit is set to small value

["Aleksey Plekhanov (Jira)" <ji...@apache.org>]

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

Aleksey Plekhanov updated IGNITE-9386:
--------------------------------------
    Fix Version/s:     (was: 2.15)

> 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
>    Affects Versions: 2.10
>            Reporter: Alexey Scherbakov
>            Assignee: Rodion Smolnikov
>            Priority: Major
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> 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.20.10#820010)