[
https://issues.apache.org/jira/browse/IGNITE-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493082#comment-15493082
]
Vladislav Pyatkov edited comment on IGNITE-3138 at 9/15/16 11:48 AM:
---------------------------------------------------------------------
I have added queue, which stores exception between flushing of a Streamer.
If streamer invokes {{flush()}} (or {{close()}}) method, first exception (which
have occurred a place during time when Streamer worked) will be thrown out, all
other exception will poled from queue and added on the first, as a suppressed.
You can set size of stored history of exceptions, using
{{exceptionHistorySize}} property.
was (Author: v.pyatkov):
I have added queue, which stores exception between flushing of a Streamer.
If streamer invokes {{flush()}} (or {{close()}}) method, first exception (which
have occurred a place during time when Streamer worked) will be thrown out, all
other exception will poled from queue and added on the first, as a suppressed.
> IgniteDataStreamer: failures are not shown on the streaming side
> ----------------------------------------------------------------
>
> Key: IGNITE-3138
> URL: https://issues.apache.org/jira/browse/IGNITE-3138
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Magda
> Assignee: Vladislav Pyatkov
> Attachments: DataStreamerFailuresTest.java
>
>
> If an exception happens during the streaming, the side that streams the data
> won't printed out anything in its logs even if IGNITE_QUIET set to false.
> This makes it's inconvenient to see whether there an issue happened during
> the streaming or not.
> Suggested improvements:
> - print out errors that happened during the streaming on the streaming side;
> - Future that is returned from {{addData}} methods is not called in case of
> error. This must be fixed. So that the user is able to write a custom logic
> around this feature and process errors somehow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
