flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mingleizhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8687) MaterializedCollectStreamResult#retrievePage should take resultLock
Date Wed, 07 Mar 2018 02:07:00 GMT

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

mingleizhang commented on FLINK-8687:

Thanks [~yuzhihong@gmail.com] , actually, I do not know the multi-thread scenario either,
I just use GUESS, or MIGHT be, as there is a {{resultLock}}. So, I think there will be many
{{write}} multi-thread, in this issue, it is {{updatePage}}. I even did not know that the
class or method in gateway package will encounter multi-thread accessing. Hmm....

> MaterializedCollectStreamResult#retrievePage should take resultLock
> -------------------------------------------------------------------
>                 Key: FLINK-8687
>                 URL: https://issues.apache.org/jira/browse/FLINK-8687
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: mingleizhang
>            Priority: Major
> Currently MaterializedCollectStreamResult#retrievePage checks page range and calls snapshot.subList()
without holding resultLock.
> {{resultLock}} should be taken.

This message was sent by Atlassian JIRA

View raw message