You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladislav Pyatkov (JIRA)" <ji...@apache.org> on 2016/06/15 12:00:14 UTC

[jira] [Assigned] (IGNITE-3055) IgniteDataStreamer can't be timed out

     [ https://issues.apache.org/jira/browse/IGNITE-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladislav Pyatkov reassigned IGNITE-3055:
-----------------------------------------

    Assignee: Vladislav Pyatkov  (was: Valentin Kulichenko)

> 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)