Project

General

Profile

Feature #5974

Improve the robustness of the automatic pause & resume mechanism

Added by Kurt Biery over 5 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Needed Enhancements
Target version:
Start date:
04/21/2014
Due date:
% Done:

0%

Estimated time:
40.00 h
Experiment:
Co-Assignees:
Duration:

Description

At the moment, we provide the ability for users to specify a maximum file size or duration. The way that this is accomplished is by the disk-writing Aggregator checking the size or duration of the disk file that is currently being written, and when the desired size or duration is reached, the Aggregator sends Pause and then Resume messages to all of the processes in the system. This has the advantage of draining the events from the system.

The mechanism that the Aggregator uses to send the Pause and Resume messages is to send XMLRPC messages, just like Run Control. This means that there is the possibility of problems, though, since Run Control could be sending a series of Pause or Resume or Stop messages at the same time that the Aggregator is sending Pause or Resume messages. We see such issues occasionally in the DS-50 DAQ.

This issue may go away if we move to a model where the art RootOutput module can internally handle the switching from one file to another (this is mentioned in Issue #5961).

History

#1 Updated by Eric Flumerfelt almost 3 years ago

  • Status changed from New to Rejected

This issue is superseded by #14516.

#2 Updated by Eric Flumerfelt almost 3 years ago

  • Category set to Needed Enhancements
  • Target version deleted (576)

#3 Updated by Eric Flumerfelt almost 3 years ago

  • Target version set to v2_00_00


Also available in: Atom PDF