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

ASF GitHub Bot commented on IGNITE-8905:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/4288


> Incorrect assertion in GridDhtPartitionsExchangeFuture
> ------------------------------------------------------
>
>                 Key: IGNITE-8905
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8905
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Sergey Chugunov
>            Assignee: Sergey Chugunov
>            Priority: Major
>             Fix For: 2.7
>
>   Original Estimate: 2h
>          Time Spent: 2h
>  Remaining Estimate: 59m
>
> Assertion was added as part IGNITE-8657 into GridDhtPartitionsExchangeFuture 
> which is correct only in situation when client has to reconnect due to too 
> short EXCHANGE_HISTORY.
> Exceptions from other situations like not being able to acquire file lock are 
> also passed to client node in FullMessage.
> This assertion should be removed and check should be introduced instead: if 
> this exception is intended to be thrown on current client node, we should do 
> this, otherwise old program flow should be executed.



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

Reply via email to