Difference between revisions of "DNS and Failover"

From Dryad wiki
Jump to: navigation, search
(Other notes)
Line 1: Line 1:
Dryad's failover system is manage by [https://www.mcnc.org MCNC]. During outages of the primary Dryad server, the failover system re-routes traffic to a secondary server.
Dryad's failover system is managed by [https://www.mcnc.org MCNC]. During outages of the primary Dryad server, the failover system re-routes traffic to a secondary server.

Revision as of 05:24, 9 August 2013

Dryad's failover system is managed by MCNC. During outages of the primary Dryad server, the failover system re-routes traffic to a secondary server.


  • Provide one way replication to a read only copy of the primary datadryad.org server
  • Make replication as close to real time as possible
  • Make failover to the secondary server and failback to the primary server automatic

This page focuses on the process for failover. For details about the servers that serve as primary and secondary, see WG:Server Setup.

Detecting Failure

Failover is based on http HEAD requests. If the Dryad server returns a 200 status, the primary site is considered "up". If not, MCNC sends all new DNS requests to the secondary server until the primary server responds again. When the primary server successfully responds to a HEAD request, DNS lookups are reverted to point at the primary server.


What happens during a failure

  • During a failure of the primary server, all datadryad.org requests go to the secondary server.
  • Apache is configured on the secondary server to disallow logins or submission of data.
    • The Dryad pages have login/submission features replaced with messages saying the feature is currently disabled.
    • If users try to access a login/submission URL directly (e.g., using a link from an integrated journal), a static HTML page is displayed. This page explains that submissions are currently disabled.

Secondary server

Since this website is read only and needs to always be up, Apache is caching pages for 5 minutes

Apache mod_rewrite and mod_substitute disable logins to this instance of Dryad

Files replicate by rsync and PGSQL replicates using Bucardo.

Keeping secondary server in sync

There is a cron job on the secondary server (root account) that performs the rsync every minute: /root/scripts/rsync-from-ncsu.sh

If the sync email (nightly cronjob on this system to sysadmin@nescent.org) shows that PGSQL tables are out of sync, then on the secondary server run these commands to resync all tables:

bucardo_ctl update sync dryad_delta_sync onetimecopy=1
bucardo_ctl reload dryad_delta_sync
bucardo_ctl status dryad_delta_sync


  • As member universities of MCNC, Duke and NCSU have free access to MCNC's Cisco GSS systems. These systems are redundant and very reliable. MCNC has configured the servers for DNS based failover from the primary to the secondary datadryad.org systems.
  • All traffic between the two servers goes through IPSEC to encrypt all data transfer (and keep from getting blocked by the Duke Intrustion Prevention System)
  • If IP addresses used for the failover change, contact MCNC - https://www.mcnc.org/support/contact.html They are a 24x7 operation so should always be reachable.
  • To disable the failover, log into namecheap with the nescent account (password is in KeePass which Helpdesk and Sysadmin have access to) and change the DNS records for datadryad.org
  1. datadryad.org to an A record for
  2. www.datadryad.org to an A record for
  3. delete second NS record for www.datadryad.org

Forcing a failover

It is useful to force the failover system during upgrades and other system activity. This keeps the system readable as much as possible.

The failover system can be forced by blocking the MCNC's access to detect the primary server. On the primary server, enter these commands:

sudo iptables -I INPUT -s -j DROP
sudo iptables -I INPUT -s -j DROP

To restorce MCNC's access to the primary server, type:

sudo /etc/init.d/iptables restart

Other notes

Ideas for improvement:

  • See Trello card on cloud architecture
  • We need to have solr run in a separate instance of tomcat or jetty or upgrade to the latest solr before this will work. Jetty would probably use less memory.
  • If we don't want to depend on a third party like MCNC or want more extensive "health" checks, we could set up a virtual machine (or two) at a cloud host such as EC2 and use it for failover.  This would allow for more extensive testing of the primary site in order to trigger a failover.  I have used this in the past (http://cbonte.github.com/haproxy-dconv/configuration-1.4.html#4-http-check expect) and it can trigger failover based on a string in the HTTP response similar to our current Nagios heath checks.  This would also be inexpensive ($50-$100/month) as the virtual machines could be very small such as EC2 micro instances.  Large data transfers could go directly to the primary server rather than through the load balancer and thus would not count against any bandwidth quotas.
  • Rather than rsync, we could use something like glusterfs or csync or unison for real time two-way file replication.  This would require extensive testing and be much more complex, but is a mature technology and widely used - http://www.gluster.org/community/documentation/index.php/Gluster_3.2:_Managing_GlusterFS_Geo-replication.  I am have been using glusterfs on 8 old DSCR nodes we used for OpenSim.
  • If we want to stick with MCNC or another failover service using HTTP status for heath checks, we could set up Nagios health checks of the production site that would shut down Apache and trigger a failover if a certain string is not on the website.
  • Use two way database replication.  Bucardo supports this and the basics could be set up fairly easily, but would require much testing.
  • Make the failover site read/write.  If we control the failover process, we could make the secondary server read/write.  Before we would switch back to the primary, we could sync files and the database back from the secondary to the primary.  This would involve some down time and more complication, but it doable.
  • SOLR 4 (in alpha as of 8/2012) should handle master-master replication.  Currently SOLR can only perform master-slave replication.


Current rsync settings:

nice -n 11 ionice -c2 -n7 rsync -ahW --progress --stats --delete --exclude 'solr/' --exclude 'access.log*' --exclude 'tivoli/' --exclude 'log/' /opt/ secundus.datadryad.org:/opt/

These items could be synced on a weekly basis or when needed:

rsync -ahW --progress --stats --delete --exclude 'largeFilesToDeposit/' --exclude 'memcpu_dump/' /home/ dryad-dev.nescent.org:/home/
#after changes to production configuration
rsync -ahW --progress --stats --delete --exclude 'access.log*' --exclude 'tivoli/' --exclude 'log/' /opt/ dryad-dev.nescent.org:/opt/
rsync -ahW --progress --stats --delete /usr/local/apache-tomcat-6.0.33/ dryad-dev.nescent.org:/usr/local/apache-tomcat-6.0.33/
rsync -ahW --progress --stats --delete --exclude='logs/' --exclude='temp/' --exclude='newrelic/' /var/tomcat/ dryad-dev.nescent.org:/var/tomcat/
rsync -ahW --progress --stats --delete /usr/java/ dryad-dev.nescent.org:/usr/java/
rsync -ahW --progress --stats --delete /var/www/dryad/ dryad-dev.nescent.org:/var/www/dryad/
#only run during setup
#rsync -avhW --progress --stats --delete /etc/httpd/ dryad-dev.nescent.org:/etc/httpd/