Open felixmaximilian opened 8 years ago
Thanks @felixmaximilian for the report. The trouble is that increasing EBS volume size requires AMIs to be rebuilt for all the regions.
One workaround might be to build Spark on the ephemeral disk at /mnt
. Could you see if that works and if so we can make a code change for that ?
Building spark in /mnt/ is possible. Do you plan to copy the compiled spark back to the EBS volume? Then its necessary to make sure you don't copy the whole target folder etc. We should build the distribution (make-distribution.sh) in /mnt/ and than uncompress it back to the EBS volume. What do you think? We could try to jointly find a comfortable solution on Monday. Have a nice weekend.
Just for the record, I'm running into this issue as well.
@felixmaximilian - Have you made any progress on solving this? I can help you write a patch, if you are interested in writing one.
A colleague created an ami with much more (I guess ebs) space on the main partition (root). Haven't really tried it again but it should be solved though.
Fixing this problem within the code of ec2 spark wasn't very much successful on my side. Tried different things but ended with the problem that you cannot really do much on the externally mounted mnt2 mnt3 etc while starting the cluster because they are added and removed during the process. Didn't really get it why. (Idea was to build it on external storage and to copy it back to root then). We can give it another try with combined forces :)
But another question : is 8gb on the root partition really enough if just the installation files fit there!? What is about the hdfs in the ephemeral folder? As far as I can remember this is also existing in root which means we can hardly save anything to the hdfs, right? It might be worth to resize all the Amis to a bigger partition or have at least another partition from the very beginning to be able to do stuff there. Nicholas Chammas notifications@github.com schrieb am Do., 5. Nov. 2015 um 20:51:
Just for the record, I'm running into this issue as well.
@felixmaximilian https://github.com/felixmaximilian - Have you made any progress on solving this? I can help you write a patch, if you are interested in writing one.
— Reply to this email directly or view it on GitHub https://github.com/amplab/spark-ec2/issues/17#issuecomment-154171456.
Hmm, anything that requires updating all the spark-ec2 AMIs is a tough sell since that takes a lot of work and the process is not automated.
Yeah just to clear some things - AFAIK to increase root partition size needs an AMI rebuild. However I think we should be able to clone and build Spark on /mnt using make-distribution.sh
and then unzip to the root partition.
The HDFS thing is not really an issue -- the HDFS binaries are on /root but it uses /mnt on every machine for storage, so it can use all the ephemeral storage.
I think this issue can be resolved without having to do any work on the AMIs. See this comment.
+1
Hi,
I am having trouble creating the spark cluster with a custom spark version. I am doing:
-v is using a specific git commit with the given hash (e.g. Spark Version 1.5.1)
When the cluster nodes are started spark is cloned from git (into /root folder) and built. After a while, the script stops because of "no space left on device" warnings. When I login into master and check the space left:
So there are 1.4 GB left on device, but when trying to download a big file, it fails again with the "no space left on device" message.
I realised that the inodes are the restricting factor here:
Can someone help me increasing the root disk volume? It might be good to increase the standard volume size such that spark can be built.