MonitorArchiver::Controller Interface Reference

import "MonitorArchiverIF.idl";

Inheritance diagram for MonitorArchiver::Controller:

Collaboration diagram for MonitorArchiver::Controller:

List of all members.

Public Member Functions
void	registerCollector (in string collectorCompName)
void	deregisterCollector (in string collectorCompName)
void	registerKnownCollectors (in string blobberCompName)

---

Detailed Description

The monitor controller brings together the collector and blobber components.

---

Member Function Documentation

void MonitorArchiver::Controller::deregisterCollector

(

in string

collectorCompName

)

Monitor collector deregisters here.

void MonitorArchiver::Controller::registerCollector

(

in string

collectorCompName

)

A monitor collector registers itself using this method, so that the controller can assign a blobber to fetch data from that collector.

void MonitorArchiver::Controller::registerKnownCollectors

(

in string

blobberCompName

)

If a blobber was shut down while collectors were still assigned to the blobber, upon restart the blobber can request to get the same known collectors assigned again, which will result in calls to Blobber.addCollector.

This call will be ignored by the controller if no collectors are assigned to the blobber, so that it is safe for the blobber to call this method just in case.

Once ACS will support persistence of component state data across component instantiations, we will have to decide whether the list of collectors assigned to a blobber should be stored for recovery only by the blobber (using the new component state persistence feature), or should still be obtained from the controller.

---

The documentation for this interface was generated from the following file:

• MonitorArchiverIF.idl