[
https://issues.apache.org/jira/browse/IGNITE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345129#comment-16345129
]
ASF GitHub Bot commented on IGNITE-7569:
----------------------------------------
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/3454
IGNITE-7569 Fixed index rebuild future
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7569
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3454.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3454
----
commit b7ae9e928846e3c5ffc2ad6412f25fbeab2417b3
Author: Alexey Goncharuk <alexey.goncharuk@...>
Date: 2018-01-30T14:41:09Z
IGNITE-7569 Fixed index rebuild future
----
> Index rebuild future is created too late
> ----------------------------------------
>
> Key: IGNITE-7569
> URL: https://issues.apache.org/jira/browse/IGNITE-7569
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Alexey Goncharuk
> Assignee: Alexey Goncharuk
> Priority: Major
> Fix For: 2.5
>
>
> rebuildIndexesIfNeeded is called before the exchange future onDone method,
> which may be too late in a distributed case: a node may complete a local
> exchange and send a compute job to a remote node. In this case, if the job
> checks the index rebuild future, it may observe {{null}}.
> To fix this, we should create the future in beforeExchange, and complete it
> after the rebuild is finished.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
