<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spark on Random Ramblings</title><link>https://blog.foundev.pro/tags/Spark.html</link><description>Recent content in Spark on Random Ramblings</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 05 Apr 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.foundev.pro/tags/Spark/index.xml" rel="self" type="application/rss+xml"/><item><title>Spark job that writes to Cassandra just hangs when one node goes down?</title><link>https://blog.foundev.pro/2016/04/05/spark-job-that-writes-to-cassandra-just-hangs-when-one-node-goes-down.html</link><pubDate>Tue, 05 Apr 2016 00:00:00 +0000</pubDate><guid>https://blog.foundev.pro/2016/04/05/spark-job-that-writes-to-cassandra-just-hangs-when-one-node-goes-down.html</guid><description>&lt;h1&gt;Spark job that writes to Cassandra just hangs when one node goes down?&lt;/h1&gt;&#10;### &lt;span style="font-size: 16px;"&gt;So this was hyper obvious once I saw the executor logs and the database schema, but this had me befuddled at first and the change in behavior with one node should have made it obvious.&lt;/span&gt; {#23da}&#10;&lt;p id="f2c8"&gt;&#10; The code was simple, read a bunch of information, do some minor transformations and flush to Cassandra. This was nothing crazy. But during the users fault tolerance testing, the job would just seamingly hang indefinitely when a node was down.&#10;&lt;/p&gt;</description></item></channel></rss>