ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-4679) Consistency checks and error tracking during node joining process
Date Tue, 26 Sep 2017 12:09:00 GMT

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

Vladimir Ozerov updated IGNITE-4679:
    Fix Version/s:     (was: 2.3)

> Consistency checks and error tracking during node joining process
> -----------------------------------------------------------------
>                 Key: IGNITE-4679
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4679
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Sergey Chugunov
> h2. Notes
> Right now new node requesting to join cluster may receive reject because of failed security
> But it is possible that any *GridComponent* may have wrong configuration or internal
state that could lead to cluster instability.
> It is better to identify these situations as early as possible and fail joining process
prohibiting poison nodes to join.
> h2. Acceptance Criteria
> # API for consistency checks is proposed and approved by community.
> # BinaryMetadata cache validation is performed by coordinator. In case of any conflicts
new node joining request is rejected.
> # [Optionally] Security checks are migrated to common mechanism.

This message was sent by Atlassian JIRA

View raw message