[jira] [Commented] (IGNITE-11416) DistributedMetaStorage improvements

["Ignite TC Bot (JIRA)" <ji...@apache.org>]

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

Ignite TC Bot commented on IGNITE-11416:
----------------------------------------

{panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3410857&buildTypeId=IgniteTests24Java8_RunAll]

> DistributedMetaStorage improvements
> -----------------------------------
>
>                 Key: IGNITE-11416
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11416
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Bessonov
>            Assignee: Ivan Bessonov
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> We need following improvements:
>  * do not write the same value twice in a row, this would lead to history pollution;
>  * add "putAll" functionality on binary level, not in public API yet. This would simplify the migration in future;
>  * do not use "*HistoryItem" class for everything, this is not conventional;
>  * retrieve "dmsVer" from cluster on handshake, this would help to reduce joining node DataBag size drastically;
>  * add "isEmpty()" or "long getVersion()" method to metastorage, will be helpful for components that use it;
>  * there has to be an ability to read data on client nodes, maybe write as well, not sure yet;
>  * implement more optimal in-memory storage for history cache;
>  * start in-memory metastorage at proper time, current implementation does it a bit too late.



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