[
https://issues.apache.org/jira/browse/IGNITE-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368255#comment-15368255
]
Vladislav Pyatkov edited comment on IGNITE-3055 at 7/8/16 7:24 PM:
-------------------------------------------------------------------
Thank [~dmagda]
Added pull reuest: https://github.com/apache/ignite/pull/864
I not noticed in the comments.
I think it redundant about 1 and 2.
1 - activeFuts will by done alvays when buffer future has done (becasu it done
on listener on future of buffer)
2 - busyLock must by using in try - finaly block. Put time waiting on busyLock
only will hid an other exception.
Unit test I will add in nearest time (about 3).
was (Author: v.pyatkov):
Thank [~dmagda]
I not noticed in the comments.
I think it redundant about 1 and 2.
1 - activeFuts will by done alvays when buffer future has done (becasu it done
on listener on future of buffer)
2 - busyLock must by using in try - finaly block. Put time waiting on busyLock
only will hid an other exception.
Unit test I will add in nearest time (about 3).
> IgniteDataStreamer can't be timed out
> -------------------------------------
>
> Key: IGNITE-3055
> URL: https://issues.apache.org/jira/browse/IGNITE-3055
> Project: Ignite
> Issue Type: Bug
> Components: streaming
> Affects Versions: 1.5.0.final
> Reporter: Valentin Kulichenko
> Assignee: Vladislav Pyatkov
> Priority: Critical
> Labels: community, customer, important
> Fix For: 1.7
>
>
> In current implementation there is no way to timeout the data streamer.
> Specifically, {{addData()}} can hang on the parallel operations semaphore and
> {{close()}} can infinitely wait on one of the futures to complete.
> We should introduce the configurable timeout and fail any data streamer
> operation if it's exceeded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
