You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2018/01/31 11:33:02 UTC

[jira] [Commented] (FLINK-8534) if insert too much BucketEntry into one bucket in join of iteration will cause a error (Caused : java.io.FileNotFoundException release file error)

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

Fabian Hueske commented on FLINK-8534:
--------------------------------------

Thanks for reporting this issue.

Can you please provide the full stacktrace of the exception?
Also a program to reproduce the bug would help a lot to identify and fix the bug.

Thank you.

> if insert too much BucketEntry into one bucket in join of iteration will cause a error (Caused : java.io.FileNotFoundException release file error)
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-8534
>                 URL: https://issues.apache.org/jira/browse/FLINK-8534
>             Project: Flink
>          Issue Type: Bug
>         Environment: windows ideal 8g ram 4core i5 cpu. Flink 1.4.0
>            Reporter: zhu.qing
>            Priority: Major
>
> When insert too much entry into bucket will cause 
> spillPartition(). So 
> this.buildSideChannel = ioAccess.createBlockChannelWriter(targetChannel, bufferReturnQueue); 
> And in 
> prepareNextPartition() of reopenablemutable hash table
> furtherPartitioning = true; 
> so in 
> finalizeProbePhase()
> freeMemory.add(this.probeSideBuffer.getCurrentSegment());
> // delete the spill files
> this.probeSideChannel.close();
> System.out.println("HashPartition probeSideRecordCounter Delete");
> this.buildSideChannel.deleteChannel();
> this.probeSideChannel.deleteChannel();
> after deleteChannel the next iteartion will fail.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)