pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Aditya <aditya@grot.org>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: sfpug@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [sfpug] DATA directory on network attached storage
Date: Fri, 8 Apr 2005 19:21:36 +0000
Message-ID: <20050408192136.GD72199@mighty.grot.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0504080957220.11558@discord.dyndns.org>
References: <200502091350.24885.josh@agliodbs.com>
	<Pine.LNX.4.62.0504080957220.11558@discord.dyndns.org>

On Fri, Apr 08, 2005 at 10:01:55AM -0700, Jeff Frost wrote:
> We are currently considering the possibility of creating a warm standby 
> machine utilizing heartbeat and a network attached storage device for the 
> DATA directory.  The idea being that the warm standby machine has its 
> postmaster stopped.  When heartbeat detects the death of the master server, 
> the postmaster is started up on the warm standby using the shared DATA 
> directory. Other than the obvious problems of both postmasters 
> inadvertently attempting access at the same time, I'm curious to know if 
> anyone has tried any similar setups and what the experiences have been.  
> Specifically is the performance of gigE good enough to allow postgres to 
> perform under load with an NFS mounted DATA dir?  Are there other problems 
> I haven't thought about?  Any input would be greatly appreciated.

We (Zapatec Inc) have been running lots of Pg dbs off of a Network Appliance
fileserver (NFS TCPv3) with FreeBSD client machines for several years now with
no problems AFAICT other than insufficient bandwidth between servers and the
fileserver (for one application, www.fastbuzz.com, 100baseTX (over a private
switched network) was insufficient, but IDE-UDMA was fine, so GigE would have
worked too, but we couldn't justify purchasing a new GigE adapter for our
Netapp).

We have the same setup as you would like, allowing for warm standby(s),
however we haven't had to use them at all.

We have not, AFAICT, had any problems with the traffic over NFS as far as
reliability -- I'm sure there is a performance penalty, but the reliability
and scalability gains more than offset that.

FWIW, if I were to do this anew, I would probably opt for iSCSI over GigE with
a NetApp.

Adi



view thread (7+ messages)  latest in thread

Message-ID: <20050408192136.GD72199@mighty.grot.org>
Permalink:  ../20050408192136.GD72199@mighty.grot.org/
Also on:    postgresql.org/message-id/20050408192136.GD72199@mighty.grot.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: aditya@grot.org, jeff@frostconsultingllc.com, josh@agliodbs.com, sfpug@postgresql.org
  Subject: Re: [sfpug] DATA directory on network attached storage
  In-Reply-To: <20050408192136.GD72199@mighty.grot.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox