Can you imagine me running in circles shouting, “The sky is falling, the sky is falling?”
Replicat Lag at Chkpt: 03:21:45
Here are the trail files at target – look at how fast it is being created.
ls -alrt ./dirdat/aa*|tail -20 -rw-r----- 1 ggsuser ggsuser 499999845 Sep 29 11:09 ./dirdat/aa000020827 -rw-r----- 1 ggsuser ggsuser 499999575 Sep 29 11:09 ./dirdat/aa000020828 -rw-r----- 1 ggsuser ggsuser 499999929 Sep 29 11:10 ./dirdat/aa000020829 -rw-r----- 1 ggsuser ggsuser 499999771 Sep 29 11:11 ./dirdat/aa000020830 -rw-r----- 1 ggsuser ggsuser 499999941 Sep 29 11:11 ./dirdat/aa000020831 -rw-r----- 1 ggsuser ggsuser 499999858 Sep 29 11:12 ./dirdat/aa000020832 -rw-r----- 1 ggsuser ggsuser 499999571 Sep 29 11:12 ./dirdat/aa000020833 -rw-r----- 1 ggsuser ggsuser 499999874 Sep 29 11:13 ./dirdat/aa000020834 -rw-r----- 1 ggsuser ggsuser 499999782 Sep 29 11:14 ./dirdat/aa000020835 -rw-r----- 1 ggsuser ggsuser 499999975 Sep 29 11:14 ./dirdat/aa000020836
My hypothesis: lots of data being capture at source.
After all is said and done. The ggserr.log was mined.
Gather dates for the 10 highest number of trails created by day in 2017.
SOURCE:
grep "^2017" ggserr.log.dinh|grep "p_test.prm: Rolling over remote file"|awk '{ print $1 }'|uniq -c|sort -nrk 1|head
224 2017-09-29
147 2017-06-02
105 2017-02-28
101 2017-05-31
100 2017-03-01
98 2017-06-01
97 2017-05-18
91 2017-05-26
89 2017-07-25
85 2017-01-26
TARGET:
grep "^2017" ggserr.log.dinh|grep "r_test.prm: Switching to next trail file"|awk '{ print $1 }'|uniq -c|sort -nrk 1|head
279 2017-09-29
183 2017-02-28
174 2017-03-01
148 2017-06-02
146 2017-02-24
137 2017-08-29
137 2017-03-24
133 2017-08-11
130 2017-08-16
128 2017-03-02
Different count between source/target for 2017-09-29 is due to data being collected at different time.
