Connection Pooling for databases running on multiple machine

Connection Pooling for databases running on multiple machine

Postby Rascal1234 » Fri 22 Oct 2010 15:17

Does dotConnect support connection pooling to multiple database instances? The configuration is postgresql running on two machines in master-slave configuration utilizing Slony-I for replication. A dotConnect entity pointing to the master, and on failover, the connection goes to the next database connection, on the slave computer. Also, does dotConnect have a mechanism for a failed master to rejoin the cluster as the new slave, without a manual configuration change? I could handle this in code with two entities, but this would be unnecessary if dotConnect did this automatically. I also could handle this with a separate load-balancer as long as I wrote a script on the postgresql host to kill its connection on a postgresql failure. It dotConnect cannot do these things, then consider this topic as a new feature request.
Rascal1234
 
Posts: 4
Joined: Tue 01 Dec 2009 16:54

Postby StanislavK » Tue 26 Oct 2010 15:13

Thank you for your suggestion. At the moment, these features are not available in dotConnect for PostgreSQL.

We will investigate the possibility of implementing local failover support and the possibility of re-connecting to a slave server when the master one is not accessible.

As for the failed master re-joining the cluster as a slave, could you please specify what support for this is supposed on the client side? This functionality seems to be in responsibility of the replication system, not the data provider.
StanislavK
Devart Team
 
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Postby StanislavK » Mon 13 Dec 2010 18:03

We have implemented the local failover feature. It will be available in the nearest build of dotConnect for PostgreSQL, which we plan to release in several days.

To enable local failover, one should set the PgSqlConnection.LocalFailover property to true. The PgSqlConnection.ConnectionLost event can be used to subscribe for the event raised when the connection is lost.
StanislavK
Devart Team
 
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Postby StanislavK » Fri 17 Dec 2010 10:32

We have released the new 5.0.69 version of dotConnect for PostgreSQL where these changes are available. The new build can be downloaded from
http://www.devart.com/dotconnect/postgresql/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/

For more information about the fixes and improvements available in dotConnect for PostgreSQL 5.0.69, please refer to
http://www.devart.com/forums/viewtopic.php?t=19795
StanislavK
Devart Team
 
Posts: 1710
Joined: Thu 03 Dec 2009 10:48


Return to dotConnect for PostgreSQL