Page History

Important architectural changes concerning MC workflows in 2017.02:

For 2017.02, MC workflows such as MC_MarkedRecordManager, MC_Synchronisation and MC_RollingBarrel have been made obsolete and are automatically removed by the DatabaseInitialization tool. These components are now subprocesses of the Master-Controller and run continuously.The only remaining MC workflow shall be the Mc SystemAlerter. The McRollingBarrel runs every 10 minutes by default, and its frequency can be controlled by editing the fews.master.mc.conf and restarting the MasterController.

  <rollingbarrel>
        <heartbeat time="60" />

In 2017.02 Mc Synchronisation synchLevels can be tuned using the mcSynchronisation xml as below, the used synchlevels will be reported mastercontroller_log.txt in DEBUG mode.

 <remotemc mcid="...">
   <database>
   ...
   </database>
   <mcSynchronisation>
     <recordtype type="TimeSeries">
       <modifier>
         <synchlevel level="0"/>
         <synchlevel level="1"/>
         <synchlevel level="2"/>
         <synchlevel level="3"/>
         <synchlevel level="4"/>
         <synchlevel level="5"/>
         <synchlevel level="6"/>
         <synchlevel level="7"/>
         <synchlevel level="8"/>
         <synchlevel level="11"/>
         <synchlevel level="16"/>
       </modifier>
      </recordtype>
    </mcSynchronisation>

McSynchronization from a specific MC in 2017.02 can be disabled by outcommenting the remotemc section and restarting the MasterController.

<!--
 <remotemc mcid="...">
...   
 </remotemc>
-->

See 13 RollingBarrel_FSS (Compact index and cache files) - EOL for the FSS maintenance workflows.