[
https://issues.apache.org/jira/browse/IGNITE-11142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823117#comment-16823117
]
Ivan Rakov commented on IGNITE-11142:
-------------------------------------
Please note: --tx-info may provide false negative search results. The problem
is caused by the issue that FetchNearXidVersionJob is sent to only one server
node. In case this node doesn't have specified transaction instance, command
will result in the follwoing strange output:
{code:java}
--------------------------------------------------------------------------------
Active transactions not found.
Will try to peek history to find out whether transaction was committed / rolled
back.
Transaction was found in completed versions history of the following nodes:
TcpDiscoveryNode [id=78499646-f0d9-4271-a9e8-37ffafa00002,
addrs=[127.0.0.1], order=2, ver=2.8.0#20190418-sha1:176ea8de, isClient=false,
consistentId=gridCommandHandlerTest2]:
State: ACTIVE
TcpDiscoveryNode [id=97ebe621-c4eb-4ad7-9d7a-afdef1200001,
addrs=[127.0.0.1], order=3, ver=2.8.0#20190418-sha1:176ea8de, isClient=false,
consistentId=gridCommandHandlerTest1]:
State: ACTIVE
{code}
It's definitely a bug. Will be fixed under IGNITE-11579.
> Control.sh should print detailed information about transaction.
> ---------------------------------------------------------------
>
> Key: IGNITE-11142
> URL: https://issues.apache.org/jira/browse/IGNITE-11142
> Project: Ignite
> Issue Type: Improvement
> Reporter: Sergey Antonov
> Assignee: Ivan Rakov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 7h 20m
> Remaining Estimate: 0h
>
> We should be able to get detailed information about transactions. Approximate
> info per node:
> * Initiator node
> * Transaction state
> * Used caches
> * Used entry keys
> * Locked keys
>
> Possible command: {{control.sh --tx-info --ids txid1[txid2,...txidN]}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
