[
https://issues.apache.org/jira/browse/SCB-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liubao updated SCB-2628:
------------------------
Description:
# This will cause trouble when not properly used, see
[https://github.com/apache/servicecomb-java-chassis/issues/3165]
# This will not improve performance in actual usage: (1) will not calculate
match many times in one governance policy; (2) if used in invocation context,
most of time is not correct. e.g service A receive a request and create a
server flow control, and then requests for B, create a client flow control. If
java chassis invocation is used to implement context, will cause client flow
control not properly match and will use server flow control policy.
was:
# This will cause trouble when not properly used, see
[https://github.com/apache/servicecomb-java-chassis/issues/3165]
# This will not improve performance in actual usage: (1) will not calculate
match many times in one governance policy; (2) if used in invocation context,
most of time is not correct, see issue.
> remove invocation context for governance
> ----------------------------------------
>
> Key: SCB-2628
> URL: https://issues.apache.org/jira/browse/SCB-2628
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
> Reporter: liubao
> Assignee: liubao
> Priority: Major
> Fix For: java-chassis-2.8.0
>
>
> # This will cause trouble when not properly used, see
> [https://github.com/apache/servicecomb-java-chassis/issues/3165]
> # This will not improve performance in actual usage: (1) will not calculate
> match many times in one governance policy; (2) if used in invocation context,
> most of time is not correct. e.g service A receive a request and create a
> server flow control, and then requests for B, create a client flow control.
> If java chassis invocation is used to implement context, will cause client
> flow control not properly match and will use server flow control policy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
