System and method for planned migration of service connections

• US 9,678,995 B2
• Filed: 05/08/2014
• Issued: 06/13/2017
• Est. Priority Date: 06/06/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Zhou, Tong, Michael, Nicolas, De Lavarene, Jean
• Primary Examiner(s): Alam, Hosain
• Assistant Examiner(s): Allen, Nicholas
• Application Number:
  US14/273,192
• Publication Number:
  US 20150324354A1
• Time in Patent Office: 1,132 Days
• Field of Search: 707609
• CPC Class Codes: G06F 12/0813 with a network or matrix configuration
• CPC Class Codes: G06F 12/0815 Cache consistency protocols
• CPC Class Codes: G06F 12/0868 Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 2212/465 Structured object, e.g. database record

Abstract

A system and method for a planned migration of service connections from a first database instance to a second database instance in a clustered database. In accordance with an embodiment, a data source and connection pool enable access by a software application to a service on the first database instance. The data source is associated with a parameter specifying a delay-for-planned-draining, and a parameter specifying a planned-draining-period, which are used to rebalance connections when relocating a service. When a service is stopped on the first database instance, the connection pool receives a “service down” event from a notification service, and maintains the connections up to a time corresponding to the delay-for-planned-draining. When a “service up” event is received, the connection pool spreads migration of the connections from the first to second database instance over the planned-draining-period.

Claims

1. A system for a planned migration of service connections in a clustered database, comprising:

one or more computers with one or more processors;

a clustered database including first and second database instances and a notification service associated therewith, wherein the notification service broadcasts notifications that describe state changes in the clustered database;

an application server that includes a data source and a connection pool associated therewith, wherein the connection pool provides a plurality of connections that an application uses to connect to the first database instance for a service thereon, and wherein the data source is associated with parameters including a delay-for-planned-draining parameter and a planned-draining-period parameter for rebalancing the plurality of connections;

wherein upon receiving a notification event that the service is stopped on the first database instance, the connection pool delays migrating the plurality of connections for up to a period of delay defined by the delay-for-planned-draining parameter, and during the period of delay, the connection pool continues allocating idle connections from the connection pool to the software application; and

wherein upon receiving a notification event indicating the service is up on the second database instance, the connection pool is operable to spread migrating the plurality of connections from the first to the second database instance over a time period defined by the planned-draining-period parameter.

2. The system of claim 1, wherein the connection pool is a Universal Connection Pool (UCP) that provides access to the clustered database using JDBC.

3. The system of claim 1, wherein the clustered database is a multi-tenant database that provides a pluggable database (PDB) for a tenant on a single database instance.

4. The system of claim 3, wherein the service is a singleton service that exposes the PDB for the tenant.

5. The system of claim 1, wherein the connections in use are migrated after they are returned to the connection pool.

6. The system of claim 1, wherein if the notification event is not received when the delay-for-planned-draining elapses, the connection pool is operable to close the plurality of connections to the first database instance.

7. The system of claim 1, wherein the migration of the plurality of connections in the connection pools are equally spread over the time period defined by the planned-draining-period parameter.

8. The system of claim 1, wherein the connection pool does not receive the notification event indicating the service is up on the second database instance when the time period defined by the delay-for-planned-draining parameter elapses, each of the plurality of connections to the service on the first database instance are closed.

9. The system of claim 1, wherein the notification event indicating the service is up on the second database instance is received within the period of delay specified by the delay-for-planned-draining parameter, the connection pool immediately starts to migrate the idle connections.

10. A computer-implemented method for a planned migration of service connections in a database cluster, comprising:

providing a clustered database including first and second database instances and a notification service associated therewith, wherein the notification service broadcasts notifications that describe state changes in the clustered database;

providing an application server executing on one or more microprocessors, wherein the application server includes a data source and a connection pool associated therewith,

wherein the connection pool provides a plurality of connections that a software application uses to connect to the first database instance for a service thereon, and

wherein the data source is associated with parameters including a delay-for-planned-draining parameter and a planned-draining-period parameter for rebalancing the plurality of connections;

delaying, by the connection pool, migrating the plurality of connections for up to a period of delay defined by the delay-for-planned draining parameter in response to receiving a notification event that the service is stopped on the first database instance, wherein the connection pool continues allocating idle connections from the connection pool to the software application during the period of delay;

receiving, from the notification service, a notification event indicating the service is up on the second database instance; and

spreading migrating the plurality of connections from the first to the second database instance over a time period defined by the planned-draining-period parameter.

11. The method of claim 10, wherein the connection pool is a Universal Connection Pool (UCP) that provides access to the clustered database using JDBC.

12. The method of claim 10, wherein the clustered database is a multi-tenant database that provides a pluggable database (PDB) for a tenant on a single database instance.

13. The method of claim 12, wherein the service is a singleton service that exposes the PDB for the tenant.

14. The method of claim 10, wherein the connections in use are migrated after they are returned to the connection pool.

15. The method of claim 10, wherein if the notification event is not received when the delay-for-planned-draining elapses, the connection pool is operable to close the plurality of connections to the first database instance.

16. The method of claim 10, wherein the migration of the plurality of connections in the connection pools are equally spread over the time period defined by the planned-draining-period parameter.

17. The method of claim 10, wherein the connection pool does not receive the notification event indicating the service is up on the second database instance when the time period defined by the delay-for-planned-draining parameter elapses, each of the plurality of connections to the service on the first database instance are closed.

18. A non-transitory computer readable medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform the steps comprising:

configuring a clustered database including first and second database instances and a notification service associated therewith, wherein the notification service broadcasts notifications that describe state changes in the clustered database;

configuring an application server executing on one or more microprocessors, wherein the application server includes a data source and a connection pool associated therewith,

wherein the connection pool provides a plurality of connections that a software application uses to connect to the first database instance for a service thereon, and

wherein the data source is associated with parameters including a delay-for-planned-draining parameter and a planned-draining-period parameter for rebalancing the plurality of connections;

delaying, by the connection pool, migrating the plurality of connections for up to a period of delay defined by the delay-for-planned draining parameter in response to receiving a notification event that the service is stopped on the first database instance, wherein the connection pool continues allocating idle connections from the connection pool to the software application during the period of delay;

receiving, from the notification service, a notification event indicating the service is up on the second database instance; and

spreading migrating the plurality of connections from the first to the second database instance over a time period defined by the planned-draining-period parameter.

19. The non-transitory computer readable medium of claim 18, wherein the connections in use are migrated after they are returned to the connection pool.

20. The non-transitory computer readable medium of claim 18, wherein if the notification event is not received when the delay-for-planned-draining elapses, the connection pool is operable to close the plurality of connections to the first database instance.