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

Posted to issues@dubbo.apache.org by "Huxing Zhang (JIRA)" <ji...@apache.org> on 2019/02/03 03:24:00 UTC

[jira] [Resolved] (DUBBO-19) Metadata refactor

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

Huxing Zhang resolved DUBBO-19.
-------------------------------
    Resolution: Fixed

This issue has been fixed in Dubbo 2.7

> Metadata refactor
> -----------------
>
>                 Key: DUBBO-19
>                 URL: https://issues.apache.org/jira/browse/DUBBO-19
>             Project: Apache Dubbo
>          Issue Type: Improvement
>            Reporter: Jun Liu
>            Priority: Major
>              Labels: GSoC2018
>   Original Estimate: 1,008h
>  Remaining Estimate: 1,008h
>
> * The registry center should only store and notify necessary data that needs to be passed between providers and consumers, for example host, port, serialization type, etc.
>  * Non-essential data should stored separately and further enriched, these data usually by offline OPS systems for display purpose.
>  * Solve the "Full GC" problem caused by large scale services and url redundancy when provider list notification were triggered.
>  * Design a new runtime metadata storage structure (or reuse the current URL), properly intact with dynamic configuration center.



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