You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Menshikov (JIRA)" <ji...@apache.org> on 2017/04/03 16:30:41 UTC
[jira] [Comment Edited] (IGNITE-1948)
ClusterTopologyCheckedException can return null for retryReadyFuture()
[ https://issues.apache.org/jira/browse/IGNITE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953742#comment-15953742 ]
Alexander Menshikov edited comment on IGNITE-1948 at 4/3/17 4:29 PM:
---------------------------------------------------------------------
[~sboikov]
Okay I total recalled :)
In PR I use only checked exception.
It's not clear for me how reach both: ensure retry future not null and don't create new exception class. Do you mean make some default not null value for retry future?
was (Author: sharpler):
[~sboikov]
Okay I total recalled :)
In PR I use only checked exception.
It's not clear for me how reach both: ensure ensure retry future not null and don't create new exception class. Do you mean make some default not null value for retry future?
> ClusterTopologyCheckedException can return null for retryReadyFuture()
> ----------------------------------------------------------------------
>
> Key: IGNITE-1948
> URL: https://issues.apache.org/jira/browse/IGNITE-1948
> Project: Ignite
> Issue Type: Bug
> Components: general
> Reporter: Denis Magda
> Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> It was noted that {{ClusterTopologyCheckedException}} ready future can be null.
> Go though all the places where this kind of exception is being initialized and check why the ready future is not set in some cases.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)