A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2016; you can also visit <a rel="external noopener" href="http://web.cs.ucla.edu:80/~miryung/Publications/icse2016-gulzar-bigdebug.pdf">the original URL</a>. The file type is <code>application/pdf</code>.
BigDebug
<span title="">2016</span>
<i title="ACM Press">
<a target="_blank" rel="noopener" href="https://fatcat.wiki/container/wvv27s77dvd5flktsj246kcxwu" style="color: black;">Proceedings of the 38th International Conference on Software Engineering - ICSE '16</a>
</i>
Developers use cloud computing platforms to process a large quantity of data in parallel when developing big data analytics. Debugging the massive parallel computations that run in today's datacenters is time consuming and error-prone. To address this challenge, we design a set of interactive, real-time debugging primitives for big data processing in Apache Spark, the next generation data-intensive scalable cloud computing platform. This requires rethinking the notion of step-through debugging
<span class="external-identifiers">
<a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1145/2884781.2884813">doi:10.1145/2884781.2884813</a>
<a target="_blank" rel="external noopener" href="https://www.ncbi.nlm.nih.gov/pubmed/27390389">pmid:27390389</a>
<a target="_blank" rel="external noopener" href="https://pubmed.ncbi.nlm.nih.gov/PMC4933307/">pmcid:PMC4933307</a>
<a target="_blank" rel="external noopener" href="https://dblp.org/rec/conf/icse/GulzarIYTCMK16.html">dblp:conf/icse/GulzarIYTCMK16</a>
<a target="_blank" rel="external noopener" href="https://fatcat.wiki/release/atfa4b4cczehrkslaojivhkosi">fatcat:atfa4b4cczehrkslaojivhkosi</a>
</span>
more »
... n a traditional debugger such as gdb, because pausing the entire computation across distributed worker nodes causes significant delay and naively inspecting millions of records using a watchpoint is too time consuming for an end user. First, BIGDEBUG's simulated breakpoints and on-demand watchpoints allow users to selectively examine distributed, intermediate data on the cloud with little overhead. Second, a user can also pinpoint a crash-inducing record and selectively resume relevant sub-computations after a quick fix. Third, a user can determine the root causes of errors (or delays) at the level of individual records through a fine-grained data provenance capability. Our evaluation shows that BIGDEBUG scales to terabytes and its record-level tracing incurs less than 25% overhead on average. It determines crash culprits orders of magnitude more accurately and provides up to 100% time saving compared to the baseline replay debugger. The results show that BIGDEBUG supports debugging at interactive speeds with minimal performance impact.
<a target="_blank" rel="noopener" href="https://web.archive.org/web/20160615100440/http://web.cs.ucla.edu:80/~miryung/Publications/icse2016-gulzar-bigdebug.pdf" title="fulltext PDF download" data-goatcounter-click="serp-fulltext" data-goatcounter-title="serp-fulltext">
<button class="ui simple right pointing dropdown compact black labeled icon button serp-button">
<i class="icon ia-icon"></i>
Web Archive
[PDF]
<div class="menu fulltext-thumbnail">
<img src="https://blobs.fatcat.wiki/thumbnail/pdf/79/9a/799aa385c4f87c23ed5d150c88bf26740d1c909a.180px.jpg" alt="fulltext thumbnail" loading="lazy">
</div>
</button>
</a>
<a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1145/2884781.2884813">
<button class="ui left aligned compact blue labeled icon button serp-button">
<i class="external alternate icon"></i>
acm.org
</button>
</a>
<a target="_blank" rel="external noopener" href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4933307" title="pubmed link">
<button class="ui compact blue labeled icon button serp-button">
<i class="file alternate outline icon"></i>
pubmed.gov
</button>
</a>