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/07/10 10:11:00 UTC
[jira] [Commented] (IGNITE-8969) Unable to await partitions release
latch
[ https://issues.apache.org/jira/browse/IGNITE-8969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538350#comment-16538350 ]
ASF GitHub Bot commented on IGNITE-8969:
----------------------------------------
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4339
IGNITE-8969 Restore server latches if needed after node left the topo…
…logy.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8969
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4339.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 #4339
----
commit e0f03efc8b10e6c630433f3e6ba5bb7218714b57
Author: Anton Kalashnikov <ka...@...>
Date: 2018-07-10T10:10:14Z
IGNITE-8969 Restore server latches if needed after node left the topology.
----
> Unable to await partitions release latch
> ----------------------------------------
>
> Key: IGNITE-8969
> URL: https://issues.apache.org/jira/browse/IGNITE-8969
> Project: Ignite
> Issue Type: Test
> Reporter: Anton Kalashnikov
> Assignee: Anton Kalashnikov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Unable to await partitions release latch within timeout for ClientLatch after this node become latch coordinator after old latch coordinator was failed.
> Reproduced by TcpDiscoverySslSelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished, TcpDiscoverySslTrustedSelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)