Thanks Till, It appears to occur when a task manager crashes and restarts – A new blob-store directory gets created and the old one remains as is, and this piles up over time. Should these *old* blob-stores be manually cleared every time a task manager crashes and restarts?
Regards, Harshith From: Till Rohrmann <trohrm...@apache.org> Date: Tuesday, 26 February 2019 at 4:12 PM To: Harshith Kumar Bolar <hk...@arity.com> Cc: user <user@flink.apache.org> Subject: [External] Re: What are blobstore files and why do they keep filling up /tmp directory? Hi Harshith, the blob store files are necessary to distribute the Flink job in your cluster. After the job has been completed, they should be cleaned up. Only in the case of cluster crashes the clean up should not happen. Since Flink 1.4.2 is no longer actively supported, I would suggest to upgrade to the latest Flink version and to check whether the problem still occurs. Cheers, Till On Tue, Feb 26, 2019 at 2:48 AM Kumar Bolar, Harshith <hk...@arity.com<mailto:hk...@arity.com>> wrote: Hi all, We're running Flink on a standalone five node cluster. The /tmp/ directory keeps filling with directories starting with blobstore--*. These directories are very large (approx 1 GB) and fill up the space very quickly and the jobs fail with a No space left of device error. The files in these directories appear to be some form of binary representation of the jobs that are running on the cluster. What are these files and how do I take care of cleaning them so they don't fill up /tmp/ causing jobs to fail? Flink version: 1.4.2 Thanks, Harshith
