You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "liubao (JIRA)" <ji...@apache.org> on 2018/04/27 06:54:00 UTC
[jira] [Resolved] (SCB-503) When using WeighedResponseTimeRule,
there are some initialize and stateless access problems
[ https://issues.apache.org/jira/browse/SCB-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
liubao resolved SCB-503.
------------------------
Resolution: Fixed
Fix Version/s: java-chassis-1.0.0-m2
> When using WeighedResponseTimeRule, there are some initialize and stateless access problems
> -------------------------------------------------------------------------------------------
>
> Key: SCB-503
> URL: https://issues.apache.org/jira/browse/SCB-503
> Project: Apache ServiceComb
> Issue Type: Bug
> Reporter: liubao
> Assignee: liubao
> Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> 1. When creating WeighedResponseTimeRule, it will call loadbalance get all service lists. And when running, it also starts a deamon to maintain states and also call loadbalance get all service lists. So any state access to 'invocation' will cause problem.
> Any filter rules will avoid to use invocation for stateful filters.
>
> 2. when change WeighedResponseTimeRule to RoundRobin, it's deamon task is not destroyed and may cause resource leak if change laodbalance rule from to this frequently.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)