Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If the History Service is not active and therefore dies does not release events then these events will remain with the Controller and will fill up its journal. Events include any log output that is created from jobs and workflow instructions. Users should make an assumption about the maximum duration of an outage of the History Service during periods of high job frequency. The Controller's journal will grow as large as allowed within the limits of the file system. Due to the fact that individual log output of jobs is included and that jobs are executed at individual frequencies we cannot give an estimate of the growth rate. However, reserving a few GB disk space for both the Primary and Secondary Controllers' journals is required.

...