Page History

...

• Resilience includes support for a number of outage scenarios with automated and manual recovery.
  

  Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1518

   
• Outage Scenarios
  • Network Connection Loss
    • A connection loss between Master and Agent. The Master will retry attempts to establish the connection and to re-send requests for a number of times.
    • Connection loss includes that from the beginning the JobScheduler Master and Agent have no knowledge if the network connection failed or if a Master Service Failure occurred.
    • This scenario is intended for a connection failure that can be recovered by retry attempts to establish a connection, it is not intended to recover from an on-going network outage. 
  • Master Service Failure
    • Either a loss of the connection between Master and Agent that cannot be recovered within the number of retry attempts specified for the Network Connection Loss scenario
      • due to a server crash or
      • due to a JobScheduler Master crash.
    • Or an unplanned JobScheduler Master restart or server restart.
  • Database Connection Loss
    • A connection loss beetween Master and database:
      • for a JobScheduler Active Cluster this scenario includes a period of less than 120s during which a cluster member retries attempts to establish the connection.
      • for a JobScheduler Passive Cluster this scenario includes no restriction of duration, it can be configured to retry attempts to connect to the database endlessly.
        • factory.ini max_db_errors=0
    • Connection loss includes that the JobScheduler Master has no knowledge if the database service failed or if the connection failed.

...