Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Site updated at 2013-11-06 05:57:05 UTC

  • Loading branch information...
commit 7a5772cda0bf617fa57340876cb8dbd6de7f55c5 1 parent 8a0ac73
@dcramer authored
View
2  2013/11/05/sentry-on-riak/index.html
@@ -138,7 +138,7 @@ <h1 class="title">Sentry on Riak</h1>
<p>Now came the scary part: cycling all machines so we could reconfigure raid <strong>and</strong> adjusting the bucket&#8217;s backend to run on eleveldb. After a bit of talking and researching, we found that the best way to migrate buckets was to remove a node from the cluster, change it&#8217;s storage backend, and then have it rejoin (thus retransfering all data). Pulling the trigger on the first &#8220;leave the cluster&#8221; command was intimidating, but it worked flawlessly. From there it just required us to cycle through the machines to get them re-raided, and have them rejoin the cluster, one at a time.</p>
-<p>After about 48 hours we gone through each machine, smoothly transitioned each node to the new backend, and have plenty of capacity to get us through the forseeable future.</p>
+<p>After about 48 hours we had gone through each machine, smoothly transitioned each node to the new backend, and have plenty of capacity to get us through the forseeable future.</p>
<h1>Scaling Out</h1>
View
4 atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[David Cramer's Blog]]></title>
<link href="http://justcramer.com/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
@@ -87,7 +87,7 @@ Event.objects.bind_nodes(event_list, 'data')
<p>Now came the scary part: cycling all machines so we could reconfigure raid <strong>and</strong> adjusting the bucket&#8217;s backend to run on eleveldb. After a bit of talking and researching, we found that the best way to migrate buckets was to remove a node from the cluster, change it&#8217;s storage backend, and then have it rejoin (thus retransfering all data). Pulling the trigger on the first &#8220;leave the cluster&#8221; command was intimidating, but it worked flawlessly. From there it just required us to cycle through the machines to get them re-raided, and have them rejoin the cluster, one at a time.</p>
-<p>After about 48 hours we gone through each machine, smoothly transitioned each node to the new backend, and have plenty of capacity to get us through the forseeable future.</p>
+<p>After about 48 hours we had gone through each machine, smoothly transitioned each node to the new backend, and have plenty of capacity to get us through the forseeable future.</p>
<h1>Scaling Out</h1>
View
2  categories/ci/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: ci | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/ci/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
View
2  categories/disqus/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: disqus | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/disqus/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
View
4 categories/django/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: django | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/django/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
@@ -87,7 +87,7 @@ Event.objects.bind_nodes(event_list, 'data')
<p>Now came the scary part: cycling all machines so we could reconfigure raid <strong>and</strong> adjusting the bucket's backend to run on eleveldb. After a bit of talking and researching, we found that the best way to migrate buckets was to remove a node from the cluster, change it's storage backend, and then have it rejoin (thus retransfering all data). Pulling the trigger on the first "leave the cluster" command was intimidating, but it worked flawlessly. From there it just required us to cycle through the machines to get them re-raided, and have them rejoin the cluster, one at a time.</p>
-<p>After about 48 hours we gone through each machine, smoothly transitioned each node to the new backend, and have plenty of capacity to get us through the forseeable future.</p>
+<p>After about 48 hours we had gone through each machine, smoothly transitioned each node to the new backend, and have plenty of capacity to get us through the forseeable future.</p>
<h1>Scaling Out</h1>
View
2  categories/git/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: git | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/git/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
View
2  categories/heroku/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: heroku | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/heroku/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
View
2  categories/howto/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: howto | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/howto/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
View
2  categories/ops/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: ops | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/ops/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
View
2  categories/osx/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: osx | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/osx/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
View
2  categories/postgresql/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: postgresql | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/postgresql/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
View
2  categories/python/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: python | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/python/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
View
4 categories/sentry/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: sentry | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/sentry/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
@@ -87,7 +87,7 @@ Event.objects.bind_nodes(event_list, 'data')
<p>Now came the scary part: cycling all machines so we could reconfigure raid <strong>and</strong> adjusting the bucket's backend to run on eleveldb. After a bit of talking and researching, we found that the best way to migrate buckets was to remove a node from the cluster, change it's storage backend, and then have it rejoin (thus retransfering all data). Pulling the trigger on the first "leave the cluster" command was intimidating, but it worked flawlessly. From there it just required us to cycle through the machines to get them re-raided, and have them rejoin the cluster, one at a time.</p>
-<p>After about 48 hours we gone through each machine, smoothly transitioned each node to the new backend, and have plenty of capacity to get us through the forseeable future.</p>
+<p>After about 48 hours we had gone through each machine, smoothly transitioned each node to the new backend, and have plenty of capacity to get us through the forseeable future.</p>
<h1>Scaling Out</h1>
View
2  categories/solr/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: solr | David Cramer's Blog]]></title>
<link href="http://justcramer.com/categories/solr/atom.xml" rel="self"/>
<link href="http://justcramer.com/"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
<author>
<name><![CDATA[David Cramer]]></name>
View
2  disqus.xml
@@ -2,7 +2,7 @@
<feed xmlns="http://www.w3.org/2005/Atom">
<title>JustCramer</title>
<link href="http://justcramer.com/atom.xml" rel="self"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
View
2  django.xml
@@ -2,7 +2,7 @@
<feed xmlns="http://www.w3.org/2005/Atom">
<title>JustCramer</title>
<link href="http://justcramer.com/atom.xml" rel="self"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
View
2  feeds/disqus.xml
@@ -2,7 +2,7 @@
<feed xmlns="http://www.w3.org/2005/Atom">
<title>JustCramer</title>
<link href="http://justcramer.com/atom.xml" rel="self"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
View
2  feeds/django.xml
@@ -2,7 +2,7 @@
<feed xmlns="http://www.w3.org/2005/Atom">
<title>JustCramer</title>
<link href="http://justcramer.com/atom.xml" rel="self"/>
- <updated>2013-11-05T21:55:34-08:00</updated>
+ <updated>2013-11-05T21:56:46-08:00</updated>
<id>http://justcramer.com/</id>
View
2  index.html
@@ -142,7 +142,7 @@ <h1 class="title"><a href="/2013/11/05/sentry-on-riak">Sentry on Riak</a></h1>
<p>Now came the scary part: cycling all machines so we could reconfigure raid <strong>and</strong> adjusting the bucket&#8217;s backend to run on eleveldb. After a bit of talking and researching, we found that the best way to migrate buckets was to remove a node from the cluster, change it&#8217;s storage backend, and then have it rejoin (thus retransfering all data). Pulling the trigger on the first &#8220;leave the cluster&#8221; command was intimidating, but it worked flawlessly. From there it just required us to cycle through the machines to get them re-raided, and have them rejoin the cluster, one at a time.</p>
-<p>After about 48 hours we gone through each machine, smoothly transitioned each node to the new backend, and have plenty of capacity to get us through the forseeable future.</p>
+<p>After about 48 hours we had gone through each machine, smoothly transitioned each node to the new backend, and have plenty of capacity to get us through the forseeable future.</p>
<h1>Scaling Out</h1>
Please sign in to comment.
Something went wrong with that request. Please try again.