[
https://issues.apache.org/jira/browse/IGNITE-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372679#comment-15372679
]
Vladislav Pyatkov commented on IGNITE-3055:
-------------------------------------------
Changes in public API:
# Added {{IgniteDataStreamer.timeout(long)}} and
{{IgniteDataStreamer.timeout()}} methods to establish timeout on streamer
operations. Default value is -1, means unlimited time.
# Added new TimeoutException (inherited IgniteException). The exception will
thrown when timeout will be reached (may be take place in
{{IgniteDataStreamer.addData(..)}}, {{IgniteDataStreamer.close()}} and
{{IgniteDataStreamer.flash()}} operations).
> 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)
