<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Distributed Systems on Infinite Script</title><link>https://www.infinitescript.com/tags/distributed-systems/</link><description>Recent content in Distributed Systems on Infinite Script</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 26 Sep 2026 20:00:00 -0700</lastBuildDate><atom:link href="https://www.infinitescript.com/tags/distributed-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>A Shared GPU Cluster with Slurm and BeeGFS</title><link>https://www.infinitescript.com/2026/09/a-shared-gpu-cluster-with-slurm-and-beegfs/</link><pubDate>Sat, 26 Sep 2026 20:00:00 -0700</pubDate><guid>https://www.infinitescript.com/2026/09/a-shared-gpu-cluster-with-slurm-and-beegfs/</guid><description>&lt;p&gt;A handful of GPU servers shared by a team tends to go through the same stages. At first people SSH into whichever machine looks idle. Then someone&amp;rsquo;s job gets killed because two people picked the same GPU. Then datasets end up copied onto every machine, each copy slightly different.&lt;/p&gt;&#10;&lt;p&gt;A job scheduler fixes the first two; a shared filesystem fixes the third. This post walks through the setup I use: one login node plus a few GPU servers, with &lt;strong&gt;Slurm&lt;/strong&gt; for scheduling, &lt;strong&gt;BeeGFS&lt;/strong&gt; for a shared &lt;code&gt;/home&lt;/code&gt;, &lt;strong&gt;UFW&lt;/strong&gt; as the host firewall, and &lt;strong&gt;Ansible&lt;/strong&gt; to keep every node consistent.&lt;/p&gt;</description></item><item><title>Consistent Hash Ring</title><link>https://www.infinitescript.com/2014/10/consistent-hash-ring/</link><pubDate>Fri, 17 Oct 2014 12:33:43 +0000</pubDate><guid>https://www.infinitescript.com/2014/10/consistent-hash-ring/</guid><description>&lt;p&gt;Consistent hashing is a special kind of hashing such that when a hash table is resized and consistent hashing is used, only K/n keys need to be remapped on average, where K is the number of keys, and n is the number of slots. In contrast, in most traditional hash tables, a change in the number of array slots causes nearly all keys to be remapped.&lt;/p&gt;&#10;&lt;p&gt;Consistent hashing achieves the same goals as Rendezvous hashing (also called HRW Hashing). The two techniques use different algorithms and were devised independently and contemporaneously.&lt;/p&gt;</description></item><item><title>Getting Started with Hadoop 2.0</title><link>https://www.infinitescript.com/2014/08/getting-started-with-hadoop-2-0/</link><pubDate>Fri, 08 Aug 2014 13:30:34 +0000</pubDate><guid>https://www.infinitescript.com/2014/08/getting-started-with-hadoop-2-0/</guid><description>&lt;p&gt;Apache™ &lt;strong&gt;Hadoop&lt;/strong&gt;® is an open source software project that enables the distributed processing of large data sets across clusters of commodity servers. It is designed to scale up from a single server to thousands of machines, with a very high degree of fault tolerance. Rather than relying on high-end hardware, the resiliency of these clusters comes from the software’s ability to detect and handle failures at the application layer.&lt;/p&gt;&#10;&lt;p&gt;Hadoop 1 popularized MapReduce programming for batch jobs and demonstrated the potential value of large scale, distributed processing. MapReduce, as implemented in Hadoop 1, can be I/O intensive, not suitable for interactive analysis, and constrained in support for graph, machine learning and on other memory intensive algorithms. Hadoop developers rewrote major components of the file system to produce Hadoop 2. To get started with the new version, it helps to understand the major differences between Hadoop 1 and 2.&lt;/p&gt;</description></item><item><title>Running Hadoop 1.1.2 on Ubuntu Linux (Single-Node Cluster)</title><link>https://www.infinitescript.com/2013/06/running-hadoop-1-1-2-on-ubuntu-linux-single-node-cluster/</link><pubDate>Fri, 14 Jun 2013 13:15:21 +0000</pubDate><guid>https://www.infinitescript.com/2013/06/running-hadoop-1-1-2-on-ubuntu-linux-single-node-cluster/</guid><description>&lt;p&gt;In this tutorial I will describe the required steps for setting up a &lt;em&gt;pseudo-distributed, single-node&lt;/em&gt; Hadoop cluster backed by the Hadoop Distributed File System, running on Ubuntu Linux.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; This walkthrough targets &lt;strong&gt;Hadoop 1.1.2&lt;/strong&gt; (2013) on Ubuntu 13.04, both long past end-of-life. Hadoop 1.x predates YARN, so the JobTracker/TaskTracker daemons, the &lt;code&gt;conf/&lt;/code&gt; layout, and config keys such as &lt;code&gt;fs.default.name&lt;/code&gt; and &lt;code&gt;mapred.job.tracker&lt;/code&gt; no longer apply to current releases (3.x uses &lt;code&gt;etc/hadoop/&lt;/code&gt;, &lt;code&gt;fs.defaultFS&lt;/code&gt;, and different web-UI ports). It is kept here as a historical reference; if you are setting up Hadoop today, follow the official &lt;a href="https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/SingleCluster.html"&gt;Single Node Cluster&lt;/a&gt; guide instead.&lt;/p&gt;</description></item></channel></rss>