[ 
https://issues.apache.org/jira/browse/IGNITE-10640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717100#comment-16717100
 ] 

ASF GitHub Bot commented on IGNITE-10640:
-----------------------------------------

GitHub user ibessonov opened a pull request:

    https://github.com/apache/ignite/pull/5637

    IGNITE-10640 Create cluster-wide MetaStorage analogue

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-10640

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/5637.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 #5637
    
----
commit 941a713a756a72d2f68e6b47caeb332dd6a62e08
Author: ibessonov <bessonov.ip@...>
Date:   2018-12-11T13:12:07Z

    IGNITE-10640 API/implementation draft + several tests.

----


> Create cluster-wide MetaStorage analogue
> ----------------------------------------
>
>                 Key: IGNITE-10640
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10640
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Ivan Bessonov
>            Assignee: Ivan Bessonov
>            Priority: Major
>
> Issues like IGNITE-8571 require the ability to store and update some 
> properties consistently on the whole cluster. It is proposed to implement 
> generic was of doing this. Main requirements:
>  * read / write / delete;
>  * surviving node / cluster restart;
>  * consistency;
>  * ability to add listeners on changing properties.
> First implementation is going to be based on local MetaStorage to guarantee 
> data persistence. Existing MetaStorage API is a subject to change as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to