[
https://issues.apache.org/jira/browse/IGNITE-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387311#comment-15387311
]
Denis Magda commented on IGNITE-3138:
-------------------------------------
Vlad,
I recalled the situations when saw streaming hanging on {{addData}} method
calls:
- server wasn't able to reply to the client, that was loading the data, because
of firewall configuration specificities. We won't be able to detect this
situation on the loading side thus it must be processed by the application
layer with the usage of {{IgniteDataStreamer.timeout()}}.
- server disconnected during the loading. Try to add one more test when a
client is loading the data and all the servers are stopped in the middle.
Additional comments are the following:
- I've updated your {{DataStreamerFailuresTest}}. Let's include it in our test
suites in any case. It's good to have it.
- If an application code doesn't use futures to wait for loading results then
in case when an exception happens (like in your newly created test) there won't
be any error related message on the *client* side at all. I would print errors
on the client side if {{IGNITE_QUIET}} is set to {{false}};
- Let's add {{setMaxRecap}} parameter to the public API and add additional
tests for it.
> 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)
