40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Thu Feb 26 13:17:31 2015, ericq, Update, Computer Scripts / Programs, FB IO load 
    Reply  Thu Feb 26 13:55:59 2015, jamie, Update, Computer Scripts / Programs, FB IO load 
       Reply  Mon Mar 23 19:30:36 2015, rana, Update, Computer Scripts / Programs, rsync frames to LDAS cluster 
          Reply  Wed May 13 09:17:28 2015, rana, Update, Computer Scripts / Programs, rsync frames to LDAS cluster 
             Reply  Mon May 18 14:22:05 2015, ericq, Update, Computer Scripts / Programs, rsync frames to LDAS cluster 
Message ID: 11288     Entry time: Wed May 13 09:17:28 2015     In reply to: 11161     Reply to this: 11299
Author: rana 
Type: Update 
Category: Computer Scripts / Programs 
Subject: rsync frames to LDAS cluster 

Still seems to be running without causing FB issues. One thought is that we could look through the FB status channel trends and see if there is some excess of FB problems at 10 min after the hour to see if its causing problems.

I also looked into our minute trend situation. Looks like the files are comrpessed and have checksum enabled. The size changes sometimes, but its roughly 35 MB per hour. So 840 MB per day.

According to the wiper.pl script, its trying to keep the minute-trend directory to below some fixed fraction of the total /frames disk. The comment in the scripts says 0.005%,

but I'm dubious since that's only 13TB*5e-5 = 600 MB, and that would only keep us for a day. Maybe the comment should read 0.5% instead...

Quote:

The rsync job to sync our frames over to the cluster has been on a 20 MB/s BW limit for awhile now.

Dan Kozak has now set up a cronjob to do this at 10 min after the hour, every hour. Let's see how this goes.

You can find the script and its logfile name by doing 'crontab -l' on nodus.

 

ELOG V3.1.3-