You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2023/01/25 12:28:00 UTC

[jira] [Resolved] (IGNITE-18061) Design placement driver

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

Alexander Lapin resolved IGNITE-18061.
--------------------------------------
    Resolution: Fixed

> Design placement driver
> -----------------------
>
>                 Key: IGNITE-18061
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18061
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Alexander Lapin
>            Assignee: Alexander Lapin
>            Priority: Major
>              Labels: ignite-3
>
> h3. Motivation
> Well, requirements are a bit hazy.  Placement driver should definitely:
>  * Provide engine for primary replica selection and failover.
>  * Either itself of, indirectly through replicas, generate notifications about primary replica change.
>  * Answer the question of primary replica placement(mapping to the ClusterNode), and corresponding lease interval in assumption that there'll be leases.
>  * Answer the question of non-primary replicas placment.
>  * Answer the question about replication group state. Is majority available? Is  replication(raft) server up and running for the particular replica? etc.
> h3. Definition of Done 
>  * Requirements to the placement driver are clear.
>  * The contract of the placement driver and its area of responsibility is defined. 
>  * Aforementioned contract meets all known requirements.
>  * Design is ready.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)