Automatic mode switching in a synchronous replication environment

A Relational Database Management System (RDMS) comprising:

• one or more computer processors;
• and
• a replication agent executed by the one or more computer processors to perform operations comprising:
• determining a first replication mode associated with a replication agent;
• identifying a triggering event;
• determining that the triggering event indicates a change in the first replication mode of the replication agent;
• responsive to determining that the triggering event indicates a change in the first replication mode, determining a second replication mode, the second replication mode being a different replication mode than the first replication mode;
• in response to determining the triggering event, identifying a set of database tasks being processed in parallel, one or more database tasks of the set of database tasks being associated with a database change;
• determining a task replication mode for at least one of the one or more database tasks;
• replicating the database change to an external replication component according to the second replication mode;
• and
• passing a notification to the one or more database tasks of the set of database tasks associated with the database change, the notification simulating the first replication mode regardless of receipt of confirmation from the external replication component.

A non-transitory machine-readable medium that stores instructions which, when performed by one or more processors of a machine, cause the machine to perform operations comprising:

• determining a first replication mode associated with a replication agent;
• identifying a triggering event;
• determining that the triggering event indicates a change in the first replication mode of the replication agent;
• responsive to determining that the triggering event indicates a change in the first replication mode, determining a second replication mode, the second replication mode being a different replication mode than the first replication mode;
• in response to determining the triggering event, identifying a set of database tasks being processed in parallel, one or more database tasks of the set of database tasks being associated with a database change;
• determining a task replication mode for at least one of the one or more database tasks;
• replicating the database change to an external replication component according to the second replication mode;
• and
• passing a notification to the one or more database tasks of the set of database tasks associated with the database change, the notification simulating the first replication mode regardless of receipt of confirmation from the external replication component.