[
https://issues.apache.org/jira/browse/TRAFODION-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931316#comment-15931316
]
Oliver Bucaojit commented on TRAFODION-2449:
--------------------------------------------
Thanks Sean.
I reviewed the existing code further and to get it to work, the logic in
HBaseTxClient.callRequestRegionInfo() to HashMapArray.addElement() will have to
be redone since it doesn't correctly add the transactions by txID. In addition
a change to tm.cpp while processing each transaction since what is there
processes only one region per transaction.
The v1 patch uploaded earlier will be able to print 1 region per txn, the (more
significant) work outlined above is still needed for additional regions.
Another enhancement idea for the command would be to print the begin/end keys
for each region. That would be helpful for debugging to understand the region
boundaries.
> dtmci - Enhance to include HBase-related info for status
> ---------------------------------------------------------
>
> Key: TRAFODION-2449
> URL: https://issues.apache.org/jira/browse/TRAFODION-2449
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: dtm
> Affects Versions: 2.2-incubating
> Reporter: Oliver Bucaojit
> Priority: Minor
> Attachments: TRAFODION-2449.v1.patch
>
>
> Request for enhancement
> dtmci 'status trans' does not show information regarding table name,
> regionserver, or region. It would be beneficial for troubleshooting and
> understanding the path taken by a transaction to include HBase related
> information.
> Initial idea would be to add a 'detailed' option to specifying the trans id.
> DTMCI > status trans <transid>, detailed
> Looking at the code, this work would require adding JNI calls from the tm
> process to the HBaseTxClient class to gather this information.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
