ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (IGNITE-1334) Issues with concurrent node stop and cache stop
Date Tue, 01 Sep 2015 06:00:51 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Semen Boikov closed IGNITE-1334.
    Assignee:     (was: Semen Boikov)

> Issues with concurrent node stop and cache stop
> -----------------------------------------------
>                 Key: IGNITE-1334
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1334
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Semen Boikov
>            Priority: Critical
>             Fix For: ignite-1.4
> There are two issue when cache is destroyed concurrently with node stop:
> 1. onKernalStop can be called twice for the same cache, it causes hang (for example GridCacheQueryManager.onKernalStop
- second attempt to block busyLock which is already blocked will hang).
> 2. If some exchanges are still in progress GridDhtPartitionsExchangeFutures are completed
with error, I see that at least initFut listener created in the 'onReceive(final UUID nodeId,
final GridDhtPartitionsFullMessage msg)' does not check initFut result.

This message was sent by Atlassian JIRA

View raw message