|
From: Michael P. <mic...@gm...> - 2013-01-24 22:37:18
|
On Fri, Jan 25, 2013 at 3:20 AM, Steven Vaughan < ste...@da...> wrote: > > Howdy, I was watching the GTM's log on a completely idle cluster (in > fact it's just now being built - there are absolutely zero clients > performing zero reads or writes) ... and I see a global txn id go by about > every 30 seconds : > > For example : > > 1:139937565083392:2013-01-24 18:14:41.802 UTC -LOG: Assigning new > transaction ID = 10158 > LOCATION: GTM_GetGlobalTransactionIdMulti, gtm_txn.c:581 > 1:139937565083392:2013-01-24 18:14:41.802 UTC -LOG: Sending transaction > ids from 10158 to 10159 > LOCATION: ProcessBeginTransactionGetGXIDCommandMulti, gtm_txn.c:1465 > 1:139937483585280:2013-01-24 18:15:10.863 UTC -LOG: Assigning new > transaction ID = 10159 > LOCATION: GTM_GetGlobalTransactionIdMulti, gtm_txn.c:581 > 1:139937483585280:2013-01-24 18:15:10.863 UTC -LOG: Sending transaction > ids from 10159 to 10160 > LOCATION: ProcessBeginTransactionGetGXIDCommandMulti, gtm_txn.c:1465 > 1:139937565083392:2013-01-24 18:15:11.838 UTC -LOG: Assigning new > transaction ID = 10160 > LOCATION: GTM_GetGlobalTransactionIdMulti, gtm_txn.c:581 > > ...is this a normal heartbeat / synchronization signal or is there > something unexpected going on? This cluster consists of precisely one GTM > (on machine 1) and one GTM_Proxy, Coordinator, and Datanode (all on machine > 2). > You have also automatic transactions in your cluster with autovacuum workers. So this is normal. -- Michael Paquier http://michael.otacoo.com |