db1,db2 migration to db5,db6 [#2392021]

Comment #1

basic CreditAttribution: basic commented 11 December 2014 at 22:12

Servers are configured and replicating, ready for deployment and promotion to primary database servers.

Log in or register to post comments

Comment #2

basic CreditAttribution: basic commented 16 December 2014 at 01:24

Status:

Active

» Fixed

db5 and db6 are configured with percona replication manager, pacemaker and corosync, and are now serving production traffic

Log in or register to post comments

Comment #3

30 December 2014 at 01:34

Status:

Fixed

» Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Log in or register to post comments

Comment #4

basic CreditAttribution: basic commented 5 January 2015 at 19:09

Adding for documentation...

The host names for access to Drupal.org's database have changed. If you were previously connecting to db1 or db2 to directly query the database, you should update your methods to use:

db6-reader-vip.drupal.org: secondary read-only access
db5-reader-vip.drupal.org: primary read-only access
db5-writer-vip.drupal.org: primary read/write access

These are listed in the preferred order. db6-reader-vip should work for 99.99% of use cases. If you cannot handle a few milliseconds of replication delay, then use db5-reader-vip. You should not need to write to the database, but db5-writer-vip can be used for this... you should come forward and tell me if you are doing this so we can disable your access :-)