Received: by 10.224.108.202 with SMTP id g10mr9032114qap.8.1340022829814;
        Mon, 18 Jun 2012 05:33:49 -0700 (PDT)
X-BeenThere: mongodb-user@googlegroups.com
Received: by 10.229.78.138 with SMTP id l10ls321797qck.4.gmail; Mon, 18 Jun
 2012 05:33:37 -0700 (PDT)
Received: by 10.224.188.8 with SMTP id cy8mr9095845qab.6.1340022817686;
        Mon, 18 Jun 2012 05:33:37 -0700 (PDT)
Received: by 10.224.204.73 with SMTP id fl9msqab;
        Mon, 18 Jun 2012 05:10:54 -0700 (PDT)
Received: by 10.52.34.9 with SMTP id v9mr804172vdi.9.1340021454280;
        Mon, 18 Jun 2012 05:10:54 -0700 (PDT)
Date: Mon, 18 Jun 2012 05:10:53 -0700 (PDT)
From: Oskar Liljeblad <os...@osk.mine.nu>
To: mongodb-user@googlegroups.com
Message-Id: <6c2d2191-0714-4d8a-92c2-580d9f9bafe6@googlegroups.com>
Subject: replicate set upgrade without downtime?
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1139_18347390.1340021453938"

------=_Part_1139_18347390.1340021453938
Content-Type: multipart/alternative; 
	boundary="----=_Part_1140_32908488.1340021453938"

------=_Part_1140_32908488.1340021453938
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

It is possible to upgrade a MongoDB replica set without downtime? The 
reason I ask is because I followed the instructions on 
http://www.mongodb.org/display/DOCS/2.0+Release+Notes#2.0ReleaseNotes-Upgrading 
to upgrade secondaries, then use db.shutdownServer() on primary. The only 
problem is that when I shut down the secondary, existing (read-only) client 
connections were disconnected. And when I issued db.shutdownServer() on the 
primary, there was small delay (10-20 seconds or so) when no server was 
primary (or so at least it seemed). Is it possible to slowly drain 
connection from a server?

Regards,

Oskar Liljeblad

------=_Part_1140_32908488.1340021453938
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

It is possible to upgrade a MongoDB replica set without downtime? The reason I ask is because I followed the instructions on http://www.mongodb.org/display/DOCS/2.0+Release+Notes#2.0ReleaseNotes-Upgrading to upgrade secondaries, then use db.shutdownServer() on primary. The only problem is that when I shut down the secondary, existing (read-only) client connections were disconnected. And when I issued db.shutdownServer() on the primary, there was small delay (10-20 seconds or so) when no server was primary (or so at least it seemed). Is it possible to slowly drain connection from a server?<br><br>Regards,<br><br>Oskar Liljeblad<br>
------=_Part_1140_32908488.1340021453938--

------=_Part_1139_18347390.1340021453938--