[
https://issues.apache.org/jira/browse/TRAFODION-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Bucaojit updated TRAFODION-2449:
---------------------------------------
Attachment: TRAFODION-2449.v1.patch
Attaching TRAFODION-2449.v1.patch
Initial patch with changes to implement:
dtmci> status regions
There is one major logic bug in the code that makes it so only one region per
transaction will be printed. Changes to the JNI will be needed to pass back
the number of regions per transaction from HashMapArray and a method to get all
regions for a transaction ID. Feel free to provide feedback or fixes.
Here is an example of the current working output for status regions after
starting 2 transactions on different tables:
$ dtmci
DTM Command line interface. v 3.1.0, Nov 26, 2014
DTMCI > status regions
Transid Status RegionId Hostname
Port TableName
----------------------------------------------------------------------------------------------
(0,150002) ACTIVE 1482796769259 localhost.localdomain 46571
TRAFODION.SEABASE.T1
----------------------------------------------------------------------------------------------
(0,150003) ACTIVE 1489084362416 localhost.localdomain 46571
TRAFODION.SEABASE.T2
DTMCI >
> 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)
