JMX operations for recovery (ISPN-994) - infinispan-dev - Jboss List Archives

2025

January

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

JMX operations for recovery (ISPN-994)

TxRecovery design update

Spring Infinispan finished for now

Mircea Markus

Monday, 4 April 2011 Mon, 4 Apr '11

1:46 p.m.

Hi, After taking it with Jonathan here is the list of JMX operations I want to add for recovery: http://community.jboss.org/wiki/Transactionrecoverydesign#JMX_tooling_for... Any feedback appreciated. Cheers, Mircea

Attachments:

attachment.html (text/html — 604 bytes)

Reply

Show replies by date

Galder Zamarreño

Monday, 4 April Mon, 4 Apr

6:37 p.m.

Mircea, What's the formatId:int and branchQualifier:byte[]? Where does the SA get this info from? Also, I'd assume that globalTxId:byte[] to the byte[] returned as part of showInDoubtTransactions() ? Cheers, On Apr 4, 2011, at 1:46 PM, Mircea Markus wrote:

Hi, After taking it with Jonathan here is the list of JMX operations I want to add for recovery: http://community.jboss.org/wiki/Transactionrecoverydesign#JMX_tooling_for... Any feedback appreciated. Cheers, Mircea _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

-- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache

Reply

Mircea Markus

6:58 p.m.

On 4 Apr 2011, at 17:37, Galder Zamarreño wrote:

Mircea, What's the formatId:int and branchQualifier:byte[]? Where does the SA get this info from?

This is the definition of the xid: http://download.oracle.com/javaee/1.3/api/javax/transaction/xa/Xid.html It is received from the TM

Also, I'd assume that globalTxId:byte[] to the byte[] returned as part of showInDoubtTransactions() ?

showInDoubtTransaction returns the Xid which includes globalTxXid.

Cheers, On Apr 4, 2011, at 1:46 PM, Mircea Markus wrote: > Hi, > > After taking it with Jonathan here is the list of JMX operations I want to add for recovery: http://community.jboss.org/wiki/Transactionrecoverydesign#JMX_tooling_for... > Any feedback appreciated. > > Cheers, > Mircea > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Reply

Galder Zamarreño

Tuesday, 5 April Tue, 5 Apr

10:38 a.m.

On Apr 4, 2011, at 6:58 PM, Mircea Markus wrote:

On 4 Apr 2011, at 17:37, Galder Zamarreño wrote: > Mircea, > > What's the formatId:int and branchQualifier:byte[]? Where does the SA get this info from? This is the definition of the xid: http://download.oracle.com/javaee/1.3/api/javax/transaction/xa/Xid.html It is received from the TM

Right, I think I understand what you mean now. I think that then: showInDoubtTransactions(): (xid:Xid, internalId:Long, status:String) Should really be: showInDoubtTransactions(): (formatId:int, branchQualifier:byte[], globalTxId:byte[], internalId:Long, status:String) Correct? Otherwise, if you really wanna leave as showInDoubtTransactions returning xid:Xid, then it'd make sense having: forceRollback(xid: Xid) : String forceCommit(xid: Xid) : String Wouldn't it?

> > Also, I'd assume that globalTxId:byte[] to the byte[] returned as part of showInDoubtTransactions() ? showInDoubtTransaction returns the Xid which includes globalTxXid. > > Cheers, > > On Apr 4, 2011, at 1:46 PM, Mircea Markus wrote: > >> Hi, >> >> After taking it with Jonathan here is the list of JMX operations I want to add for recovery: http://community.jboss.org/wiki/Transactionrecoverydesign#JMX_tooling_for... >> Any feedback appreciated. >> >> Cheers, >> Mircea >> >> >> _______________________________________________ >> infinispan-dev mailing list >> infinispan-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > > -- > Galder Zamarreño > Sr. Software Engineer > Infinispan, JBoss Cache > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

-- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache

Reply

Manik Surtani

Monday, 18 April Mon, 18 Apr

11:57 a.m.

How do you generate the Long internalID of an XID? Another approach may be to take the byte[] (XID) and Base64 it. Then you have a 1-to-1 mapping between the XID and a JMX-friendly String. :-) Or maybe an SHA1 hash of the byte[]. On 4 Apr 2011, at 12:46, Mircea Markus wrote:

Hi, After taking it with Jonathan here is the list of JMX operations I want to add for recovery: http://community.jboss.org/wiki/Transactionrecoverydesign#JMX_tooling_for... Any feedback appreciated. Cheers, Mircea _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

-- Manik Surtani manik(a)jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org

Reply

Mircea Markus

1:05 p.m.

On 18 Apr 2011, at 10:57, Manik Surtani wrote:

How do you generate the Long internalID of an XID?

I'va factorised the IdGenerator(now ClusterIdGenerator) galder wrote for generating cluster-unique longs for HR's versioned operations.

Another approach may be to take the byte[] (XID) and Base64 it. Then you have a 1-to-1 mapping between the XID and a JMX-friendly String. :-) Or maybe an SHA1 hash of the byte[].

yes,that would work as well. A long is smaller and (not that matters a lot) cheaper to generate.

On 4 Apr 2011, at 12:46, Mircea Markus wrote: > Hi, > > After taking it with Jonathan here is the list of JMX operations I want to add for recovery: http://community.jboss.org/wiki/Transactionrecoverydesign#JMX_tooling_for... > Any feedback appreciated. > > Cheers, > Mircea > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani manik(a)jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Reply

Manik Surtani

1:39 p.m.

On 18 Apr 2011, at 12:05, Mircea Markus wrote:

> Another approach may be to take the byte[] (XID) and Base64 it. Then you have a 1-to-1 mapping between the XID and a JMX-friendly String. :-) Or maybe an SHA1 hash of the byte[]. yes,that would work as well. A long is smaller and (not that matters a lot) cheaper to generate.

But it could roll over (yes, I know unlikely), and you also have the issue of encoding the node that generates the long into the long which is open to corruption if nodes join/leave and the cluster size is large. But it's no biggie, works for now basically. Just keep in mind that in future a more robust/direct 1-to-1 mapping between XID and some JMX-friendly representation may be necessary. -- Manik Surtani manik(a)jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org

Reply

5008

days inactive

5022

days old

infinispan-dev@lists.jboss.org

Manage subscription

6 comments

3 participants

tags (0)

participants (3)

Galder Zamarreño
Manik Surtani
Mircea Markus