Revision as of 19:03, July 25, 2017 by Bonniem (talk | contribs) (→‎Prerequisites)
Jump to: navigation, search

GRACEFUL ROLLOVER

Staring with Release 8.1.400.??, URS simplifies the process for moving call processing from one URS instance to another URS. Once a working/active primary/backup pairs of URSes exist, URS automatically performs all necessary steps for a graceful rollover using those relationships.

How It Works

When a graceful rollover starts, Management Layer still sees the primary/backup pair relationship between the two URSs, but internally those URSes turn into a cluster of two independent URSes, which can stop to execute the graceful rollover commands.

Prerequisites

The prerequisites for a graceful rollover are as follows:

  • A primary/backup URSes must be configured and work. Graceful shutdown is not applicable for single (backup less) URS instance.
  • Genesys recommends configuring agent reservation before using graceful rollover since the graceful rollover process temporarily turns a primary/backup pair of URSes into a cluster of two independent URSs. For more information, see the agent_reservation option in the Universal Routing 8.1 Reference Manual.
  • If Orchestration Server backed up calls are present, verify that the current backup URS "sees" all such calls. This can be achieved with a web request to the primary URS: urs/console?backup. <br<,br>The response will be “name(host:port,socket);0000000000000000”, The presence of a not null connection id after the semicolon indicates that it is not safe to start the rollover process as some ORS backed up calls can be lost..

Graceful Rollover Command

Graceful rollover can be started with one of the following:

  • A web request to current primary URS urs/console?rollover
  • With console command rollover
  • Through the Local Control Agent command Suspend (Graceful Stop)

When a graceful rollover command is received: The current primary URS:

  • stops processing of new interactions (from TServers or Web clients).
  • stops processing of any multimedia calls (returns them back into Ixn queues) and ORS backed up calls.
  • imitates switching into backup mode of operation forcing ORS (if any) to switch to current backup node.

The current backup URS:

  • deletes all interactions (as they all will be processed by the current primary node) except for the ORS backed-up interactions.
  • switches into primary mode of operation and starst processing new interactions as they arrive.

When the original primary finishes processing of all existing calls it automatically exits.

When graceful shutdown is started with command rollover - if there is no backup configured then URS will reply with no backup and will not start graceful shutdown procedure - if URS has no connection with its backup then URS will reply with no connection and will not start graceful shutdown procedure 

- URS will reply with name of its backup server and starts graceful shutdown procedure.

When graceful shutdown is started through LCA URS will just ignore request if there is no proper backup. Effectively it will result in not graceful shutdown as SCS in such case will request application to quit.


Detailed Design

Comments or questions about this documentation? Contact us for support!