You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "humingcheng (Jira)" <ji...@apache.org> on 2020/02/05 08:09:00 UTC
[jira] [Updated] (SCB-1742) Optimize Aggregator and etcd's service
discovery cache mechanism
[ https://issues.apache.org/jira/browse/SCB-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
humingcheng updated SCB-1742:
-----------------------------
Description:
Optimize the second level cache of instance, in package server.service.cache.
Schenario
We only use the cache and not call the backend directly when using Aggregatory adaptor, as Aggregator does not guarantee accuracy when querying the backend.
For etcd adaptor, if the backend is unavailable, the cache content is returned instead of a backend error.
was:
We only use the cache and not call the backend directly when using Aggregator for service discovery, as Aggregator does not guarantee accuracy when querying the backend.
For etcd, If the backend is unavailable, the cache content is returned instead of a backend error.
> Optimize Aggregator and etcd's service discovery cache mechanism
> ----------------------------------------------------------------
>
> Key: SCB-1742
> URL: https://issues.apache.org/jira/browse/SCB-1742
> Project: Apache ServiceComb
> Issue Type: Improvement
> Components: Service-Center
> Reporter: humingcheng
> Assignee: humingcheng
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Optimize the second level cache of instance, in package server.service.cache.
> Schenario
> We only use the cache and not call the backend directly when using Aggregatory adaptor, as Aggregator does not guarantee accuracy when querying the backend.
> For etcd adaptor, if the backend is unavailable, the cache content is returned instead of a backend error.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)