Brandon Van Ryswyk

<p>Here at Datastax, my fellow intern Daniel Chin and I built a 32 node DataStax Enterprise cluster running on Raspberry Pi’s! We are showcasing the always on, fault tolerant nature of Cassandra by letting anybody take down an entire data center with the press of a Big Red Button in our lobby.</p>

<p dir="ltr"><img alt="lobby_wide" class="size-large wp-image-25336 alignleft" height="407" src="https://www.datastax.com/sites/default/files/content/blog/past_blogs/past_dev_blogs/20140819_devblog_lobby_wide.jpg" width="700" /></p>

<p dir="ltr">Being able to withstand a data center going down is <a href="https://www.datastax.com/2014/08/disaster-recovery-not-disaster-recovery" title="Disaster Avoidance, Not Disaster Recovery">not just an edge case</a>, <a href="https://www.datastax.com/2014/05/nooutages-the-world-of-the-immortal-online-application" title="#NoOutages- The world of the immortal online application">it is an absolute necessity</a> for the highly available applications Cassandra powers. While the cloud is far more flexible for production use, nothing beats a big shiny hardware display for a demo.</p>

<p dir="ltr">Our main goal for this project was to take the abstract concept of fault tolerance and make it something you can see in action and interact with.&nbsp;We built upon the work of Travis Price and the DataStax Sales Engineering team, who pioneered the use of Raspberry Pi's to demonstrate Cassandra.</p>

<p dir="ltr"><img alt="cluster_closeup_final" class="alignnone size-large wp-image-25335" src="https://www.datastax.com/sites/default/files/content/blog/past_blogs/past_dev_blogs/20140819_devblog_cluster_closeup_final-700x461.jpg" /></p>

<h2 dir="ltr">The Build Process:</h2>

<h3 dir="ltr">The Hardware:</h3>

<p dir="ltr">&nbsp;We wanted the overall display to look clean and professional enough to be appropriate for the lobby at our headquarters, but expose enough of the technology to be a compelling and unique demo.</p>

<p dir="ltr">As DataStax is a software company, fabricating hardware came with a unique set of challenges. ("Hey, do we have a shop vac?" "No.") I ended up drawing on my experience with Solidworks (a popular CAD program) from high school FIRST robotics to design all of the acrylic, and had it cut using a laser&nbsp;at a local machine shop. The assorted mounting hardware and the pedestal were sourced from McMaster Carr.</p>

<p dir="ltr"><img alt="lots_of_pis" class="alignnone size-large wp-image-25313" src="https://www.datastax.com/sites/default/files/content/blog/past_blogs/past_dev_blogs/20140819_devblog_lots_of_pis-700x525.jpg" /></p>

<h3 dir="ltr">The Electronics:</h3>

<p dir="ltr">Each Pi is running at its factory clock settings, and is completely unmodified. To avoid latency problems and to ensure our Pi's stayed online, we transitioned off of WiFi and used ethernet cables and switches instead.</p>

<p dir="ltr">To get power to each Pi, we use micro USB cables that are connected to five port USB hubs that are then plugged in to two power strips, one for each data center. This makes it easy to set up, and doesn't require building any custom power distribution rails.</p>

<p dir="ltr">Our large red button is connected to an Arduino that actuates a power relay to cut AC power to the network switch for Datacenter RED. The Arduino provides timing control, and makes the button inoperable during the network outage.</p>

<p dir="ltr">\<img alt="daniel_assembling" class="alignnone size-large wp-image-25312" src="https://www.datastax.com/sites/default/files/content/blog/past_blogs/past_dev_blogs/20140819_devblog_daniel_assembling-700x525.jpg" /></p>

<h3 dir="ltr">The Software:</h3>

<p dir="ltr">The cluster is set up as a two datacenter DSE 4.5 cluster, with Opscenter 5.0 running to show the status of all the nodes. As we expected, running a high performance enterprise database on a computer with a single core 700mHz processor and 512MB of RAM is not trivial.</p>

<p dir="ltr">We are using vnodes, and have throttled all of the cassandra.yaml values to the lowest intensity we can to squeeze C* to within our hardware constraints.</p>

<p dir="ltr">With Cassandra running, each Pi has 8 to 11 megabytes of free RAM.</p>

<p dir="ltr">For reference, our documentation currently recommends 16 cores and 24GB of RAM for a production system.</p>

<p><img alt="cables_wall" class="alignnone size-large wp-image-25311" src="https://www.datastax.com/sites/default/files/content/blog/past_blogs/past_dev_blogs/20140819_devblog_cables_wall-700x518.jpg" /> While this cluster won't be setting speed benchmarks any time soon, we&nbsp;hope that it gets people excited about Cassandra and its incredible always on capabilities! <img alt="pedestal_pic_teaser" class="alignnone size-large wp-image-25353" src="https://www.datastax.com/sites/default/files/content/blog/past_blogs/past_dev_blogs/20140819_devblog_pedestal_pic_teaser-700x466.jpg" /></p>


Multi-Datacenter Cassandra on 32 Raspberry Pi’s

Brandon Van Ryswyk

Discover more

Share

More Technology

Why You Can't Miss Cassandra Summit

Mitigate the OpenAI Debacle with Open Source and Cloud

Supercharge AI Assistants with Superagent and DataStax

DataStax and AWS: Accelerating GenAI Applications into Production

NoSQL and Vector DB
for Generative AI,
Instantly, At Scale

Brandon Van Ryswyk

Discover more

Share

More Technology

Why You Can't Miss Cassandra Summit

Mitigate the OpenAI Debacle with Open Source and Cloud

Supercharge AI Assistants with Superagent and DataStax

DataStax and AWS: Accelerating GenAI Applications into Production

NoSQL and Vector DBfor Generative AI,Instantly, At Scale

NoSQL and Vector DB
for Generative AI,
Instantly, At Scale