You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2018/03/15 12:51:00 UTC

[jira] [Commented] (IGNITE-7962) More cases of suppressed exceptions in IsolatedUpdater

    [ https://issues.apache.org/jira/browse/IGNITE-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16400342#comment-16400342 ] 

Dmitriy Setrakyan commented on IGNITE-7962:
-------------------------------------------

We must make sure that whatever changes are made to the data streamer, the performance should not degrade. Please make sure to aggressively benchmark before and after the change to ensure that there is no effect on the performance.

> More cases of suppressed exceptions in IsolatedUpdater
> ------------------------------------------------------
>
>                 Key: IGNITE-7962
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7962
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.4
>            Reporter: Ilya Kasnacheev
>            Assignee: Ilya Kasnacheev
>            Priority: Major
>
> IsolatedUpdater is a StreamReciever.
> The contract for StreamReciever.recieve() is, @throws org.apache.ignite.IgniteException If failed.
> However, there's a number of cases where this doesn't happen and exceptions are suppressed after being written in server log. Should replace (or augment) log.error()'s with throw new IgniteException().
> See maillist discussion.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)