ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Scherbakov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-9386) control.sh --tx can produce confusing results when limit is set to small value
Date Mon, 27 Aug 2018 10:50:00 GMT
Alexei Scherbakov created IGNITE-9386:
-----------------------------------------

             Summary: 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
            Reporter: Alexei Scherbakov


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
(v7.6.3#76005)

Mime
View raw message