You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/28 13:41:00 UTC
[jira] [Commented] (IGNITE-8482) Skip 2-phase partition release
wait in case of activation or dynamic caches start
[ https://issues.apache.org/jira/browse/IGNITE-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492685#comment-16492685 ]
ASF GitHub Bot commented on IGNITE-8482:
----------------------------------------
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4078
IGNITE-8482 2-phase partition release wait optimization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8482
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4078.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 #4078
----
commit b9bef2d655bd8fea9ab4976577532029979b462f
Author: Pavel Kovalenko <jo...@...>
Date: 2018-05-28T13:36:19Z
IGNITE-8482 Do not perform distributed partition release wait in case of cluster activation or caches start.
commit 66dd1c5795f80aa8a8f775633f8f1b2ab9c5b2fd
Author: Pavel Kovalenko <jo...@...>
Date: 2018-05-28T13:38:51Z
IGNITE-8482 Skip partitions validation in case of caches start.
----
> Skip 2-phase partition release wait in case of activation or dynamic caches start
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-8482
> URL: https://issues.apache.org/jira/browse/IGNITE-8482
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 2.5
> Reporter: Pavel Kovalenko
> Assignee: Pavel Kovalenko
> Priority: Major
> Fix For: 2.6
>
>
> Currently we perform 2-phase partitions release waiting on any type of distributed exchange. We can optimize this behaviour, skipping such waiting on cluster activation (obviously if we activate cluster it means that before activation no caches were running and there is no reason to wait for finishing operations) and on dynamic caches start.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)