Versions Compared

Key

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

...

  • Process classes can be used as a means to implement high availability:
    • Display feature availability
      StartingFromRelease1.8
    • A sequence of JobScheduler Agents can be specified that would be checked for availability by the initiating JobScheduler instance at run-time.
    • If a JobScheduler Agent were not avaiable then the next Agent would be selected for execution of a job. The configuration is made from the <remote_schedulers select="first|next"/> attribute.
    • The connection to an Agent makes use of the HTTP or HTTPS protocol; i.e. the remote instance is configured by http://host:port or https://host:port .
  • Example
    • Agent Passive Cluster configuration

      Code Block
      languagexml
      titleProcess class for Use fixed-priority scheduling with Agents
      collapsetrue
      <?xml version="1.0" encoding="ISO-8859-1"?>
      <process_class  max_processes="10"/>
          <remote_schedulers select="first">
              <remote_scheduler remote_scheduler="http://Andreas-MacBook-Pro.local:4445" http_heartbeat_timeout="15" http_heartbeat_period="10"/>
              <remote_scheduler remote_scheduler="http://localhost:4445" http_heartbeat_timeout="15" http_heartbeat_period="10"/>
          </remote_schedulers>
      </process_class>
    • Agent Active Cluster configuration

      Code Block
      languagexml
      titleProcess class for round-robin scheduling with Agents
      collapsetrue
      <?xml version="1.0" encoding="ISO-8859-1"?>
      <process_class  max_processes="10"/>
          <remote_schedulers select="next">
              <remote_scheduler remote_scheduler="http://Andreas-MacBook-Pro.local:4445" http_heartbeat_timeout="15" http_heartbeat_period="10"/>
              <remote_scheduler remote_scheduler="http://localhost:4445" http_heartbeat_timeout="15" http_heartbeat_period="10"/>
          </remote_schedulers>
      </process_class>

...