X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 08CAB53CC3; Fri, 8 Apr 2005 20:21:47 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 18994-01; Fri, 8 Apr 2005 19:21:38 +0000 (GMT) Received: from mighty.grot.org (66-117-150-96.web.lmi.net [66.117.150.96]) by svr1.postgresql.org (Postfix) with ESMTP id D8B66537A4; Fri, 8 Apr 2005 20:21:36 +0100 (BST) Received: by mighty.grot.org (Postfix, from userid 515) id F1D7B5D6A; Fri, 8 Apr 2005 19:21:36 +0000 (GMT) Date: Fri, 8 Apr 2005 19:21:36 +0000 From: Aditya To: Jeff Frost Cc: Josh Berkus , sfpug@postgresql.org, pgsql-performance@postgresql.org Subject: Re: [sfpug] DATA directory on network attached storage Message-ID: <20050408192136.GD72199@mighty.grot.org> References: <200502091350.24885.josh@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200504/201 X-Sequence-Number: 11598 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