[jira] [Comment Edited] (IGNITE-8084) Unlock write lock in DataStreamerImpl

["Ivan Fedotov (JIRA)" <ji...@apache.org>]

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

Ivan Fedotov edited comment on IGNITE-8084 at 5/7/18 7:26 AM:
--------------------------------------------------------------

Was implemented according to ticket IGNITE-6699 'Optimize client-side data streamer performance' [1].

[1] https://issues.apache.org/jira/browse/IGNITE-6699


was (Author: ivanan.fed):
Was implemented according to ticket IGNITW-6699 'Optimize client-side data streamer performance' [1].

[1] https://issues.apache.org/jira/browse/IGNITE-6699

> Unlock write lock in DataStreamerImpl
> -------------------------------------
>
>                 Key: IGNITE-8084
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8084
>             Project: Ignite
>          Issue Type: Improvement
>          Components: streaming
>            Reporter: Ivan Fedotov
>            Assignee: Ivan Fedotov
>            Priority: Major
>              Labels: usability
>             Fix For: 2.6
>
>
> In method DataStreamerImpl.CloseEx there is wrire lock without unlock [1]. I think this behavior is based on impossibility to call after closing other public method of DataStreamer, that use read lock.
> It's not correctly that after closing streamer we don't unlock writeLock: I think that we can use *closed* flag to throw exception if streamer will be used after closing.
> [1]https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastreamer/DataStreamerImpl.java#L1217



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