[Flink 1.5.0] BlobServer data for a job is not getting cleaned up at JM

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[Flink 1.5.0] BlobServer data for a job is not getting cleaned up at JM

Amit Jain
Hi,

We are running Flink 1.5.0 rc3 with YARN as cluster manager and found
Job Manager is getting killed due to out of disk error.

Upon further analysis, we found blob server data for a job is not
getting cleaned up. Right now, we wrote directory cleanup script based
on directory creation time of job_<JOBID>.

Please suggest good way to deal with this problem. Can I raise a JIRA
ticket for same?

--
Thanks,
Amit
Reply | Threaded
Open this post in threaded view
|

Re: [Flink 1.5.0] BlobServer data for a job is not getting cleaned up at JM

Chesnay Schepler
Please open a JIRA.

On 16.05.2018 13:58, Amit Jain wrote:

> Hi,
>
> We are running Flink 1.5.0 rc3 with YARN as cluster manager and found
> Job Manager is getting killed due to out of disk error.
>
> Upon further analysis, we found blob server data for a job is not
> getting cleaned up. Right now, we wrote directory cleanup script based
> on directory creation time of job_<JOBID>.
>
> Please suggest good way to deal with this problem. Can I raise a JIRA
> ticket for same?
>
> --
> Thanks,
> Amit
>

Reply | Threaded
Open this post in threaded view
|

Re: [Flink 1.5.0] BlobServer data for a job is not getting cleaned up at JM

Amit Jain
Thanks Chesnay for the quick reply. I raised the ticket
https://issues.apache.org/jira/browse/FLINK-9381.

On Wed, May 16, 2018 at 5:33 PM, Chesnay Schepler <[hidden email]> wrote:

> Please open a JIRA.
>
>
> On 16.05.2018 13:58, Amit Jain wrote:
>>
>> Hi,
>>
>> We are running Flink 1.5.0 rc3 with YARN as cluster manager and found
>> Job Manager is getting killed due to out of disk error.
>>
>> Upon further analysis, we found blob server data for a job is not
>> getting cleaned up. Right now, we wrote directory cleanup script based
>> on directory creation time of job_<JOBID>.
>>
>> Please suggest good way to deal with this problem. Can I raise a JIRA
>> ticket for same?
>>
>> --
>> Thanks,
>> Amit
>>
>