XrdPfcResourceMonitor.cc File Reference

#include "XrdPfcResourceMonitor.hh"
#include "XrdPfc.hh"
#include "XrdPfcPathParseTools.hh"
#include "XrdPfcFsTraversal.hh"
#include "XrdPfcDirState.hh"
#include "XrdPfcDirStateSnapshot.hh"
#include "XrdPfcDirStatePurgeshot.hh"
#include "XrdPfcTrace.hh"
#include "XrdPfcPurgePin.hh"
#include "XrdOss/XrdOss.hh"
#include <algorithm>

Include dependency graph for XrdPfcResourceMonitor.cc:

Go to the source code of this file.

Namespaces
	XrdPfc

Macros
#define	dprintf(...)   (void(0))

Functions
void	XrdPfc::OldStylePurgeDriver (DataFsPurgeshot &ps)
void	Proto_ResourceMonitorHeartBeat ()

Macro Definition Documentation

dprintf

#define dprintf

(

...

)

(void(0))

Definition at line 19 of file XrdPfcResourceMonitor.cc.

Function Documentation

Proto_ResourceMonitorHeartBeat()

void Proto_ResourceMonitorHeartBeat

(

)

Definition at line 876 of file XrdPfcResourceMonitor.cc.

{
   // static const char *trc_pfx = "ResourceMonitorHeartBeat() ";
 
   // Pause before initial run
   sleep(1);
 
   // XXXX Setup initial / constant stats (total RAM, total disk, ???)
 
   XrdOucCacheStats             &S = Cache::GetInstance().Statistics;
   XrdOucCacheStats::CacheStats &X = S.X;
 
   S.Lock();
 
   X.DiskSize = Cache::Conf().m_diskTotalSpace;
 
   X.MemSize = Cache::Conf().m_RamAbsAvailable;
 
   S.UnLock();
 
   // XXXX Schedule initial disk scan, time it!
   //
   // TRACE(Info, trc_pfx << "scheduling intial disk scan.");
   // schedP->Schedule( new ScanAndPurgeJob("XrdPfc::ScanAndPurge") );
   //
   // bool scan_and_purge_running = true;
 
   // XXXX Could we really hold last-usage for all files in memory?
 
   // XXXX Think how to handle disk-full, scan/purge not finishing:
   // - start dropping things out of write queue, but only when RAM gets near full;
   // - monitoring this then becomes a high-priority job, inner loop with sleep of,
   //   say, 5 or 10 seconds.
 
   while (true)
   {
      time_t heartbeat_start = time(0);
 
      // TRACE(Info, trc_pfx << "HeartBeat starting ...");
 
      // if sumary monitoring configured, pupulate OucCacheStats:
      S.Lock();
 
      // - available / used disk space (files usage calculated elsewhere (maybe))
 
      // - RAM usage
      /* XXXX From Cache
      {  XrdSysMutexHelper lck(&m_RAM_mutex);
         X.MemUsed   = m_RAM_used;
         X.MemWriteQ = m_RAM_write_queue;
      }
      */
 
      // - files opened / closed etc
 
      // do estimate of available space
      S.UnLock();
 
      // if needed, schedule purge in a different thread.
      // purge is:
      // - deep scan + gather FSPurgeState
      // - actual purge
      //
      // this thread can continue running and, if needed, stop writing to disk
      // if purge is taking too long.
 
      // think how data is passed / synchronized between this and purge thread
 
      // !!!! think how stat collection is done and propgated upwards;
      // until now it was done once per purge-interval.
      // now stats will be added up more often, but purge will be done
      // only occasionally.
      // also, do we report cumulative values or deltas? cumulative should
      // be easier and consistent with summary data.
      // still, some are state - like disk usage, num of files.
 
      // Do we take care of directories that need to be newly added into DirState hierarchy?
      // I.e., when user creates new directories and these are covered by either full
      // spec or by root + depth declaration.
 
      int heartbeat_duration = time(0) - heartbeat_start;
 
      // TRACE(Info, trc_pfx << "HeartBeat finished, heartbeat_duration " << heartbeat_duration);
 
      // int sleep_time = m_fs_state..m_purgeInterval - heartbeat_duration;
      int sleep_time = 60 - heartbeat_duration;
      if (sleep_time > 0)
      {
         sleep(sleep_time);
      }
   }
}

References XrdPfc::Cache::Conf(), XrdOucCacheStats::CacheStats::DiskSize, XrdPfc::Cache::GetInstance(), XrdOucCacheStats::Lock(), XrdPfc::Configuration::m_diskTotalSpace, XrdPfc::Configuration::m_RamAbsAvailable, XrdOucCacheStats::CacheStats::MemSize, XrdOucCache::Statistics, XrdOucCacheStats::UnLock(), and XrdOucCacheStats::X.

Here is the call graph for this function: