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/11/19 17:56:00 UTC
[jira] [Commented] (IGNITE-10043) Lost partitions list is reset
when only one server is alive in the cluster
[ https://issues.apache.org/jira/browse/IGNITE-10043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692062#comment-16692062 ]
ASF GitHub Bot commented on IGNITE-10043:
-----------------------------------------
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/5436
IGNITE-10043 Do not reset LOST partitions when only one node is left in a cluster
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10043
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5436.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 #5436
----
commit 5f61419270ca4813e8d0edbb4c23341591fa1816
Author: sboikov <sb...@...>
Date: 2018-11-15T14:14:21Z
ignite-10043
commit 51933a8e1f3840a4e6a18e8d32de33b775a35321
Author: sboikov <sb...@...>
Date: 2018-11-15T19:04:46Z
ignite-10043
commit 9a6d642f840897f8b70dc8b7bb7d7cbfedcbd0bd
Author: sboikov <sb...@...>
Date: 2018-11-16T09:58:21Z
ignite-10043
commit fb8fd071b1d69f2cb054d3798320380eb3401362
Author: sboikov <sb...@...>
Date: 2018-11-16T13:37:04Z
merge
commit bc1ac15c36fb459f221c9b723ad82a6e43a5bfca
Author: sboikov <sb...@...>
Date: 2018-11-16T13:38:07Z
merge
commit 96e2fddc9b7c18ec11ab181ad45633f4041a9aa3
Author: ibessonov <be...@...>
Date: 2018-11-19T09:41:05Z
IGNITE-10192 Fixed OptimizedMarshallerTest#testAllocationOverflow throws OOME instead of expected IOE - Fixes #5400.
Signed-off-by: Dmitriy Govorukhin <dm...@gmail.com>
commit 166e87ed19929b9e064732752d5a5ce1069b5076
Author: Alexander Kalinin <ve...@...>
Date: 2018-11-19T09:47:12Z
IGNITE-10320 Web Console: Workaround for memory leak in chart component.
commit c9906aab8efa2c70a164fb593d9e22ef1edaa9ec
Author: ibessonov <be...@...>
Date: 2018-11-19T09:50:56Z
IGNITE-10142 Scale factor added to several tests from Cache 8 suite. - Fixes #5253.
Signed-off-by: Dmitriy Govorukhin <dm...@gmail.com>
commit 9e3bd7dd686d3392e6bbe2c7defebe260eb029f7
Author: ibessonov <be...@...>
Date: 2018-11-19T10:06:47Z
IGNITE-10197 Fixed unexpected IllegalArgumentException in IgniteDbPutGetAbstractTest#testRandomPutGetRemove - Fixes #5410.
Signed-off-by: Dmitriy Govorukhin <dm...@gmail.com>
commit a63a81a51418a8ae1dadff019d9e5eace38e1631
Author: Ilya Lantukh <il...@...>
Date: 2018-11-19T12:07:49Z
IGNITE-9558 Avoid blocking transactions on client connect when possible - Fixes #4933.
commit acfdcdaa0f667b1ebebc26cea90df030804056a7
Author: Dmitriy Govorukhin <dm...@...>
Date: 2018-11-19T13:41:28Z
IGNITE-10285 Fixed U.doInParallel may lead to deadlock - Fixes #5404.
Signed-off-by: Dmitriy Govorukhin <dm...@gmail.com>
commit c711d4f6f7ecc6ad59643a2a82d7d487d8d45a90
Author: ibessonov <be...@...>
Date: 2018-11-19T14:02:48Z
IGNITE-10321 Fix flaky test CacheContinuousWithTransformerReplicatedSelfTest.LocalEventListener - Fixes #5427.
Signed-off-by: Dmitriy Govorukhin <dm...@gmail.com>
commit a198b3ff5799899690419e3c0b6306a1eaebd6e7
Author: Max-Pudov <pu...@...>
Date: 2018-11-19T14:31:47Z
IGNITE-10098 .NET: Add missing TcpCommunicationSpi properties
This closes #5379
commit 673da458d94881874806a428bef13d829ac25cbb
Author: Alexey Goncharuk <al...@...>
Date: 2018-11-19T17:54:02Z
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite into ignite-10043
----
> Lost partitions list is reset when only one server is alive in the cluster
> --------------------------------------------------------------------------
>
> Key: IGNITE-10043
> URL: https://issues.apache.org/jira/browse/IGNITE-10043
> Project: Ignite
> Issue Type: Bug
> Reporter: Stanislav Lukyanov
> Assignee: Semen Boikov
> Priority: Major
> Fix For: 2.8
>
>
> When server nodes are killed one by one IgniteCache.lostPartitions() returns non-empty list up until there is just one node left. When only one node is alive, the lostPartitions() returns an empty collection even though the partition loss events has been fired and the partitions are missing.
> This only affects cluster with persistence enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)