[jira] [Commented] (SPARK-725) Ran out of disk space on EC2 master due to Ganglia logs

["Andrew Ash (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212022#comment-14212022 ] 

Andrew Ash commented on SPARK-725:
----------------------------------

[~joshrosen] is this still an issue for you?  I believe the Ganglia feature was removed from the published binaries due to licensing concerns so should no longer be included in the spark_ec2 scripts.  Setting an upper bound on Ganglia disk use is probably a setting on the Ganglia receiver rather than the sender (Spark) so I doubt we could do much for this in the general case from the Spark side.

> Ran out of disk space on EC2 master due to Ganglia logs
> -------------------------------------------------------
>
>                 Key: SPARK-725
>                 URL: https://issues.apache.org/jira/browse/SPARK-725
>             Project: Spark
>          Issue Type: Bug
>          Components: EC2
>    Affects Versions: 0.7.0
>            Reporter: Josh Rosen
>
> This morning, I started a Spark Standalone cluster on EC2 using 50 m1.medium instances.  When I tried to rebuild Spark ~5.5 hours later, the build failed because the master ran out of disk space.  It looks like {{/var/lib/ganglia/rrds/spark}} grew to 4.2 gigabytes, using over half of the AMI's EBS disk space.
> Is there a default setting that we can change to place a harder limit on the total amount of space used by Ganglia to prevent this from happening?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org