trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anuradha Hegde <>
Subject RE: Nifty trick
Date Fri, 04 Dec 2015 19:42:06 GMT
To debug mxosrvr you can set zktimeout
          User program ZooKeeper session timeout.
          Default 180 seconds.
      <description>ZooKeeper session timeout.
          dcs passes this to the zk quorum as suggested maximum time for a
          session (This setting becomes zookeeper's 'maxSessionTimeout').

          "The client sends a requested timeout, the server responds with
           timeout that it can give the client. " In milliseconds.


-----Original Message-----
From: Dave Birdsall []
Sent: Friday, December 4, 2015 11:40 AM
Subject: RE: Nifty trick

Cool! Which property?

-----Original Message-----
From: Selva Govindarajan []
Sent: Friday, December 4, 2015 11:39 AM
Subject: RE: Nifty trick

There is yet another way:

Issue show remoteprocess in the trafci command.

But debugging mxosrvr would a bit tricky, because zookeeper would timeout
the connection between the client and server. You need to increase the
timeout using a property in dcs-site.xml


-----Original Message-----
From: Dave Birdsall []
Sent: Friday, December 4, 2015 11:34 AM
Subject: Nifty trick


While debugging a Trafodion issue through Trafci, I came across an
interesting problem and a nifty trick to solve it.

Trafci connects to Trafodion through an mxosrvr process on platform. The
question is, how to figure out which mxosrvr process one has connected to in
order to set breakpoints. Here’s a way to figure that out:

1.       Start a dtmci, and do a “status trans” command.

2.       In your Trafci session, do a “begin work;”

3.       In dtmci, do another “status trans”. It should show an ACTIVE
transaction. In the Owner column, you’ll see the node number and Linux pid
of the mxosrvr process.

Happy debugging!


View raw message