[
https://issues.apache.org/jira/browse/IGNITE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953672#comment-15953672
]
Alexander Menshikov commented on IGNITE-1948:
---------------------------------------------
[~sboikov]
Hi Semen, I'm sorry, I real miss your answer for me.
Yes, I read Alexey's message, because he wrote it to me.
There is problem in the phrase "instead of setting a retry ready future in the
checked exception, you would set a correct affinity topology version here". But
if you see at code, you will see ready future use not for get affinity topology
version, but for waiting. So the change breaks logic. I asked Alexey about
that, but still have not got answer. Maybe you can clarify it for me.
Thank you for information about checked/unchecked. I need some time for recall
what I did in this ticked :)
> 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)
