<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>gladlyCode &#187; message queue</title>
	<atom:link href="http://gladlycode.com/tag/message-queue/feed/" rel="self" type="application/rss+xml" />
	<link>http://gladlycode.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 29 Sep 2010 03:46:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Scheduled downtime: Major server upgrade at 3 am</title>
		<link>http://gladlycode.com/2009/scheduled-downtime-server-upgrade/</link>
		<comments>http://gladlycode.com/2009/scheduled-downtime-server-upgrade/#comments</comments>
		<pubDate>Sun, 09 Aug 2009 21:16:00 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>
		<category><![CDATA[gladlyCode]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[message queue]]></category>
		<category><![CDATA[scalability]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[vertical scaling]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=36</guid>
		<description><![CDATA[
			
				
			
		
When you&#8217;re sound asleep, we&#8217;ll be performing a major upgrade to make our purple gladlyCast server harder, better, faster, stronger:

We are performing the upgrade on Aug 11 (Tuesday), at 3 am in the morning as that&#8217;s the time where the least people use our services. The update will take maximum 1 hour. If you send [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2009%2Fscheduled-downtime-server-upgrade%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2009%2Fscheduled-downtime-server-upgrade%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>When you&#8217;re sound asleep, we&#8217;ll be performing a major upgrade to make our purple <a href="http://gladlycast.com">gladlyCast</a> server harder, better, faster, stronger:</p>
<p><img class="size-full wp-image-37" title="Scaling vertically at 3 am" src="http://gladlycode.com/assets/2009/08/Bigger-server.png" alt="Scaling vertically at 3 am" width="520" height="280" /></p>
<p>We are performing the upgrade on <strong>Aug 11 (Tuesday)</strong>, at <strong>3 am</strong> in the morning as that&#8217;s the time where the least people use our services. The update will take maximum 1 hour. <strong>If you send an SMS during our downtime, it will be queued safely on another server and delivered to Twitter once our upgrade is completed.</strong></p>
<p><img class="alignnone size-full wp-image-38" title="SMS will be queued at gateway and redelivered to gladlyCast server as soon as possible." src="http://gladlycode.com/assets/2009/08/Messages-will-be-queued.png" alt="SMS will be queued at gateway and redelivered to gladlyCast server as soon as possible." width="520" height="434" /></p>
<p>No messages is expected to be lost during this transition. We treat your SMSes with care and provide refreshments to make them happy. We would update our <a href="http://twitter.com/gladlycast">gladlyCast</a> Twitter regularly during which time.</p>
<p>The <strong>August 11</strong> plan for the upgrade is to:</p>
<ol>
<li><strong>3:00 am</strong> &#8212; Pull the plug and upgrade.</li>
<li><strong>3:20 am</strong> &#8212; Move everything over and wake the server.</li>
<li><strong>3:25 am</strong> &#8212; Wake our Twitter service and redeliver all queued messages sent between 3:00 am and 3:25 am.</li>
<li><strong>3:30 am</strong> &#8212; Wake our web server with sign ups re-enabled.</li>
<li>Spend the next 30 minutes ensuring all components are functioning.</li>
</ol>
<p><em>(During this transition, this blog will go down too. This is something we haven&#8217;t thought about and I&#8217;m feeling rather dumb right now.)</em></p>
<p><strong>Update 3:30 am:</strong> Our web server is up. (:<br />
<strong>Update 3:33 am:</strong> Sign ups are not re-enabled at the moment.<br />
<strong>Update 3:43 am:</strong> Components are functional except for phone association. Still working on that one.<br />
<strong>Update 4:10 am:</strong> Sign up is re-enabled. Upgrade completed.</p>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2009/scheduled-downtime-server-upgrade/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

