• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Building a High-Availability PostgreSQL Cluster at ARIN
 

Building a High-Availability PostgreSQL Cluster at ARIN

on

  • 645 views

Through a long and intense period of research, implementation, and testing, ARIN completed the migration from Oracle to PostgreSQL late last year. Learn more at: ...

Through a long and intense period of research, implementation, and testing, ARIN completed the migration from Oracle to PostgreSQL late last year. Learn more at: http://teamarin.net/2014/04/01/building-high-availability-postgresql-cluster-arin/

Statistics

Views

Total Views
645
Views on SlideShare
636
Embed Views
9

Actions

Likes
1
Downloads
6
Comments
0

2 Embeds 9

https://twitter.com 6
http://www.slideee.com 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Building a High-Availability PostgreSQL Cluster at ARIN Building a High-Availability PostgreSQL Cluster at ARIN Presentation Transcript

    • Building a High-Availability PostgreSQL Cluster Presenter: Devon Mizelle System Administrator Co-Author: Steven Bambling System Administrator
    • What is ARIN? •Regional Internet registry for Canada, US, and parts of the Caribbean •Distributes IPv4 & IPv6 addresses and Autonomous System Numbers (Internet number resources) in the region •Provides authoritative WHOIS services for number resources in the region 2
    • ARIN’s Internal Data 3
    • Requirements 4
    • Why Not Slony or pgpool-II? • Slony replaces pgSQL‟s replication – Why do this? – Why not let pgSQL handle it? • Pgpool is not ACID-Compliant – Doesn‟t confirm writes to multiple nodes 5
    • Our solution • CMAN / Corosync – Red Hat + Open-source solution for cross- node communication • Pacemaker – Red Hat and Novell‟s solution for service management and fencing • Both under active development by Clusterlabs 6
    • CMAN/ Corosync • Provides a messaging framework between nodes • Handles a heartbeat between nodes – “Are you up and available?” – Does not provide „status‟ of service, Pacemaker does • Pacemaker uses Corosync to send messages between nodes 7
    • CMAN / Corosync 8
    • About Pacemaker • Developed / maintained by Red Hat and Novell • Scalable – Anywhere from a two-node to a 16- node setup • Scriptable – Resource scripts can be written in any language – Monitoring – Watches out for service state changes – Fencing – Disables a box and switches roles when failures occur • Shareable database between nodes about status of services / nodes 9
    • Pacemaker 10 Master AsyncSync
    • Other Pacemaker Resources 11 Fencing IP Addresses
    • How does it all tie together? From the bottom up…
    • Pacemaker 13 Client “vip”Replication “vip” Master Sync Async App
    • Event Scenario 14 Master Sync AsyncMaster SyncAsync
    • PostgreSQL • Still in charge of replicating data • The state of the service and how it starts is controlled by Pacemaker 15
    • Layout 16 💙 💙 MasterSlave Slave cman cman cman Client
    • Using Tools to Look Deeper Introspection…
    • # crm_mon -i 1 -Arf
    • # crm_mon –i 1 -Arf (cont)
    • Questions? Devon Mizelle