Providing services across systems that manage distributed replicas

• US 9,268,840 B2
• Filed: 07/31/2014
• Issued: 02/23/2016
• Est. Priority Date: 10/05/2012
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Hu, Wei-Ming, Chidambaran, Lakshminaray, Dilman, Mark, Khan, Feroz A., Mathur, Bhaskar, Neel, Kevin S., Novak, Leonid, Patel, Kant C., Stewart, Michael J., Sun, Hubert, Ramasubramanian, Saravanakumar
• Primary Examiner(s): LE, DEBBIE M
• Application Number:
  US14/448,987
• Publication Number:
  US 20150058290A1
• Time in Patent Office: 572 Days
• Field of Search: 707/703, 707/803, 707/999.202
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: H04L 41/02 Standardisation; Integration
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers

Abstract

Techniques are provided to allow users to define a global service that is offered across multiple replicated databases. Database clients connect to and use a global service just as they do with regular services on a single database today. Upon receiving a connection request, a collection of components, referred to collectively as the Global Data Service framework (GDS framework), automatically chooses the best database server instances to which to connect a client. Once those connections have been established, the clients determine which database server instance, of those database server instances to which they are connected, to send requests to based, at least in part, on advisory messages sent to the clients by the GDS framework.

Claims

1. A method comprising:

grouping a set of global service managers into a plurality of regions;

wherein the plurality of regions includes a first region and a second region;

wherein the first region includes a first set of one or more global service managers from the set of global service managers and the second region includes a second set of one or more global service managers from the set of global service managers;

wherein the first set of one or more global service managers handle service requests from clients that are local to the first region and the second set of one or more global service managers handle service requests from clients that are local to the second region;

establishing the second region as a buddy region for the first region;

determining that the first set of one or more global service managers are no longer operational; and

in response to determining that the first set of one or more global service managers are no longer operational, using at least one global service manager from the second set of one or more global service managers to handle service requests from clients that are local to the first region.

2. The method of claim 1, wherein after the first set of one or more global service managers are no longer operational, the at least one global service manager from the second set of one or more global service managers acts as a listener for the first region while continuing to act as a listener for the second region.

3. The method of claim 1,

wherein the at least one global service manager from the second set of one or more global service managers causes connection requests received from the clients that are local to the first region to be forwarded to database server instances that are in the first region;

and

wherein the at least one global service manager from the second set of one or more global service managers causes connection requests received from the clients that are local to the second region to be forwarded to database server instances that are in the second region.

4. The method of claim 1, further comprising:

receiving, at the at least one global service manager from the second set of one or more global service managers, a connection request from a client that is local to the first region;

in response to receiving the connection request, selecting at least one database service instance, from among a set of database server instances; and

wherein the selection is based, at least in part, on a determination that the client is local to the first region and one or more other selection criteria.

5. The method of claim 1, wherein the at least one global service manager from the second set of one or more global service managers generates events for the first region while the first set of one or more global service managers are no longer operational.

6. The method of claim 1, wherein the at least one global service manager from the second set of one or more global service managers computes metrics for the clients that are local to the first region and publishes the metrics to the clients that are local to the first region.

7. A method comprising:

receiving a set of one or more parameter values for a particular service within a distributed replication environment;

wherein the distributed replication environment includes a plurality of database systems, each of which maintains a separate copy of a data set associated with the particular service; and

based on the set of one or more parameter values for the particular service, performing at least one of;

determining whether a client may be connected to a database server instance that is in a region that is not local to the client;

determining whether the particular service may failover from a first database server instance to a second database server instance that is in a different region than the first database server instance;

or

determining whether replication lag for a database server instance satisfies a threshold value.

8. The method of claim 7, wherein the method comprises determining whether a client may be connected to a database server instance that is in a region that is not local to the client.

9. The method of claim 8,

wherein the set of one or more parameter values includes a locality parameter value that indicates a location restriction for routing client connection requests;

and

wherein determining whether the client may be connected to the database server instance that is in the region that is not local to the client comprises determining whether the locality parameter value restricts connections for the client to database server instances that belong to a region that is local to the client.

10. The method of claim 7, wherein the method comprises determining whether the particular service may failover from the first database server instance to the second database server instance that is in the different region than the first database server instance.

11. The method of claim 10,

wherein the set of one or more parameter values includes a parameter value that indicates that inter-region failover is permitted;

and

wherein determining whether the particular service may failover from the first database server instance to the second database server instance that is in the different region than the first database server instance comprises determining that the particular service is not available in a region that is local to the client.

12. The method of claim 7, wherein the method comprises determining whether replication lag for the database server instance satisfies a threshold value.

13. The method of claim 12,

wherein the set of one or more parameter values includes a parameter value that indicates a maximum acceptable threshold value of replication lag;

and

the method further comprising in response to determining that the replication lag of the database server instance exceeds the maximum acceptable threshold value, routing one or more clients to a different database server instance for which replication lag satisfies the maximum acceptable threshold value.

14. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of:

grouping a set of global service managers into a plurality of regions;

wherein the plurality of regions includes a first region and a second region;

wherein the first region includes a first set of one or more global service managers from the set of global service managers and the second region includes a second set of one or more global service managers from the set of global service managers;

wherein the first set of one or more global service managers handle service requests from clients that are local to the first region and the second set of one or more global service managers handle service requests from clients that are local to the second region;

establishing the second region as a buddy region for the first region;

determining that the first set of one or more global service managers are no longer operational; and

in response to determining that the first set of one or more global service managers are no longer operational, using at least one global service manager from the second set of one or more global service managers to handle service requests from clients that are local to the first region.

15. The one or more non-transitory storage media of claim 14, wherein after the first set of one or more global service managers are no longer operational, the at least one global service manager from the second set of one or more global service managers acts as a listener for the first region while continuing to act as a listener for the second region.

16. The one or more non-transitory storage media of claim 14,

wherein the at least one global service manager from the second set of one or more global service managers causes connection requests received from the clients that are local to the first region to be forwarded to database server instances that are in the first region;

and

wherein the at least one global service manager from the second set of one or more global service managers causes connection requests received from the clients that are local to the second region to be forwarded to database server instances that are in the second region.

17. The one or more non-transitory storage media of claim 14, further storing instructions that cause performance of:

receiving, at the at least one global service manager from the second set of one or more global service managers, a connection request from a client that is local to the first region;

in response to receiving the connection request, selecting at least one database service instance, from among a set of database server instances; and

wherein the selection is based, at least in part, on a determination that the client is local to the first region and one or more other selection criteria.

18. The one or more non-transitory storage media of claim 14, wherein the instructions further cause performance of the at least one global service manager from the second set of one or more global service managers generating events for the first region while the first set of one or more global service managers are no longer operational.

19. The one or more non-transitory storage media of claim 14, wherein the instructions further cause performance of the at least one global service manager from the second set of one or more global service managers computing metrics for the clients that are local to the first region and publishing the metrics to the clients that are local to the first region.

20. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of:

receiving a set of one or more parameter values for a particular service within a distributed replication environment;

wherein the distributed replication environment includes a plurality of database systems, each of which maintains a separate copy of a data set associated with the particular service; and

based on the set of one or more parameter values for the particular service, performing at least one of;

determining whether a client may be connected to a database server instance that is in a region that is not local to the client;

determining whether the particular service may failover from a first database server instance to a second database server instance that is in a different region than the first database server instance;

or

determining whether replication lag for a database server instance satisfies a threshold value.

21. The one or more non-transitory storage media of claim 20, wherein the instructions further cause performance of determining whether a client may be connected to a database server instance that is in a region that is not local to the client.

22. The one or more non-transitory storage media of claim 21,

wherein the set of one or more parameter values includes a locality parameter value that indicates a location restriction for routing client connection requests;

and

wherein instructions for determining whether the client may be connected to the database server instance that is in the region that is not local to the client comprise instructions for determining whether the locality parameter value restricts connections for the client to database server instances that belong to a region that is local to the client.

23. The one or more non-transitory storage media of claim 20, wherein the instructions further cause performance of determining whether the particular service may failover from the first database server instance to the second database server instance that is in the different region than the first database server instance.

24. The one or more non-transitory storage media of claim 23,

wherein the set of one or more parameter values includes a parameter value that indicates that inter-region failover is permitted;

and

wherein instructions for determining whether the particular service may failover from the first database server instance to the second database server instance that is in the different region than the first database server instance comprise instructions for determining that the particular service is not available in a region that is local to the client.

25. The one or more non-transitory storage media of claim 20, wherein the instructions further cause performance of determining whether replication lag for the database server instance satisfies a threshold value.

26. The one or more non-transitory storage media of claim 25,

wherein the set of one or more parameter values includes a parameter value that indicates a maximum acceptable threshold value of replication lag;

and

the instructions further cause performance of in response to determining that the replication lag of the database server instance exceeds the maximum acceptable threshold value, routing one or more clients to a different database server instance for which replication lag satisfies the maximum acceptable threshold value.