You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Chugunov (JIRA)" <ji...@apache.org> on 2018/07/02 09:45:00 UTC
[jira] [Updated] (IGNITE-8905) Incorrect assertion in
GridDhtPartitionsExchangeFuture
[ https://issues.apache.org/jira/browse/IGNITE-8905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Chugunov updated IGNITE-8905:
------------------------------------
Remaining Estimate: 4h
Original Estimate: 4h
> 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: 4h
> Remaining Estimate: 4h
>
> 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)