[jira] [Updated] (IGNITE-18525) Introduce new PlacementDriver Ignite component

["Vyacheslav Koptilin (Jira)" <ji...@apache.org>]

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

Vyacheslav Koptilin updated IGNITE-18525:
-----------------------------------------
    Labels: iep-101 ignite-3  (was: ignite-3)

> Introduce new PlacementDriver Ignite component
> ----------------------------------------------
>
>                 Key: IGNITE-18525
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18525
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexander Lapin
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>              Labels: iep-101, ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> h3. Motivation
> Placement Driver  is expected to be used as 
>  * A leaseholder tracker, or in other words, an engine for replication groups leases selection and fail-over.
>  * Distributed meta data propagator, such as safe time, will be implemented in Placement Driver [Part 2] though.
> This is an initial ticket, a sort of  utility one, that will introduce new PlacementDriver Ignite component, add corresponding dependencies wihtin mvn and gradle and incorporate the component into node start/stop flow.
> h3. Definition of Done
>  * New Placement Driver  Ignite Component is introduced along with corresponding decencies (e.g. meta storage), busy locks, etc.
>  * It's properly started and stopped withing Ignite node start/stop process.
> h3. Implementation Notes
> Pretty straightforward. The one to mention is that introducing new component will required to update tests and mocks, however because at this point placement driver does nothing it'll possible to use nulls almost everywhere.



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