search

is00hcw / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 1 forks source link

Improve monitoring of heavy traffic and large transactions #515

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What do you see instead?

Monitoring heavy traffic and large transactions is difficult, as no indication 
is given of the progress in THL transfer (when receiving large THL files).

Additional information

Reported by Giuseppe.

Original issue reported on code.google.com by linas.vi...@continuent.com on 22 Mar 2013 at 8:52

GoogleCodeExporter commented 9 years ago 
From Giuseppe:

While testing prefetch, I found myself in need of measuring how much catch-up 
the replicator has to do.

I built a quick script that gets the target as the highest seqno in the THL 
files, the latest applied sequence number from trepctl, and shows the amount 
and percentage done.

TARGET=$(~/tsb2/db$NODE/thl info | tail -n 1 | awk '{print 8 LTL}')
DONE=$(~/tsb2/db$NODE/trepctl services | grep appliedLastSeqno | awk '{print 5 
LTL}')

TODO=$(($TARGET-$DONE))
printf "Target: %8d \n" $TARGET
printf "Done : %8d \n" $DONE
printf "To do : %8d ( %4.1f%% )\n" $TODO $(echo "scale=2 ; ($TODO/$TARGET)*100" 
| bc)

Sample output:

QA.FB1 tungsten@qa[prefetch_tests]$ ./how_much_done.sh 3
Target: 1678695
Done : 132049
To do : 1546646 ( 92.0% )

QA.FB1 tungsten@qa[prefetch_tests]$ ./how_much_done.sh 3
Target: 1678695
Done : 156609
To do : 1522086 ( 90.0% )

QA.FB1 tungsten@qa[prefetch_tests]$ ./how_much_done.sh 3
Target: 1678695
Done : 369489
To do : 1309206 ( 77.0% ) 

You can see an implementation in Perl of this script at the Tungsten-Toolbox 
site.
http://code.google.com/p/tungsten-toolbox/downloads/list

The intent is to add the functionality of tungsten-progress to trepctl.

The ideal solution is to add tungsten progress features to trepctl:
https://code.google.com/p/tungsten-toolbox/downloads/detail?name=tungsten-progre
ss

Original comment by linas.vi...@continuent.com on 22 Mar 2013 at 2:15

GoogleCodeExporter commented 9 years ago 
We'll use 2.1.0 instead of 2.0.8, hence moving the issues.

Original comment by linas.vi...@continuent.com on 27 Mar 2013 at 3:14

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 7 Jun 2013 at 1:06

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 19 Jun 2013 at 5:38

GoogleCodeExporter commented 9 years ago 
Moving to 2.1.2

Original comment by linas.vi...@continuent.com on 21 Aug 2013 at 12:59

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 26 Aug 2013 at 1:54

GoogleCodeExporter commented 9 years ago 
There won't be a 2.1.3.

Original comment by linas.vi...@continuent.com on 17 Sep 2013 at 10:13

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 23 Dec 2013 at 9:51

GoogleCodeExporter commented 9 years ago 
Unscheduling. Should be brought in to future releases as planning dictates.

Original comment by linas.vi...@continuent.com on 2 May 2014 at 8:16