Skip to content

[SCB-2118]servicecomb.references.version-rule not work#2052

Merged
liubao68 merged 1 commit intoapache:masterfrom
liubao68:liubao
Nov 13, 2020
Merged

[SCB-2118]servicecomb.references.version-rule not work#2052
liubao68 merged 1 commit intoapache:masterfrom
liubao68:liubao

Conversation

@liubao68
Copy link
Contributor

Follow this checklist to help us incorporate your contribution quickly and easily:

  • Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean install -Pit to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

@liubao68 liubao68 merged commit 91af6cf into apache:master Nov 13, 2020
@jlynet
Copy link

jlynet commented Mar 26, 2022

这个是什么场景下触发的啊?我最近遇到生产上两个应用都开启的版本隔离,最后A 调B 的时候调用到B的另一个最新版本去了。具体场景是C 调用A服务采用 version-rule latest ,然后A再调用B (A调用B采用版本号区间隔离)。单B起了一个最新的版本时候,在注册中心看A居然和B最新服务有调用关系。然后A又调用不到B的最新版本,然后线程就出现很多锁和阻塞,最后服务器CPU被拉到好高。

@liubao68
Copy link
Contributor Author

你可以创建一个issue提问,描述下场景和版本, 以及出现问题的条件。 不要再已经关闭的PR或者issue里面回复。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants