diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-851798836
service-comb 应该没有那种 就是 假如 服务 频繁的发出超时请求, 底层检测到服务不可用,优雅停机下线, @liubao68
--
This is an automated message from the Apache Git Service.
To respond to the message,
liubao68 commented on issue #2398:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2398#issuecomment-851769842
按照目前的服务发现机制,这种情况是预期会发生的情况,是设计可接纳的。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
tianxiaoliang commented on issue #961:
URL:
https://github.com/apache/servicecomb-service-center/issues/961#issuecomment-851739607
方便的话请加我的微信,tianxiaoliang2017
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
tianxiaoliang merged pull request #1031:
URL: https://github.com/apache/servicecomb-service-center/pull/1031
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries
This is an automated email from the ASF dual-hosted git repository.
tianxiaoliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-service-center.git
The following commit(s) were added to refs/heads/master by this push:
new 90ad4fe SCB-2176
little-cui opened a new pull request #1031:
URL: https://github.com/apache/servicecomb-service-center/pull/1031
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/SCB)
fanjiang-2021 commented on issue #2399:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2399#issuecomment-851442132
可以实现这个接口看看 org.apache.servicecomb.loadbalance.ServerListFilterExt 类似灰度
--
This is an automated message from the Apache Git Service.
To respond to the
SenixCoder opened a new issue #2399:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2399
一个服务端存在多个实例,客户端想要根据某些条件访问指定实例(例如上一次接口调用的),该怎么去做呢?
我看文档中写到
```
Endpoint 描述当前请求需要发往的实例地址。 这个 context 参数只能够在 consumer 端的 PRC 接口使用。当
微服务存在多个实例的时候,可以使用这种方式指定将请求发往哪个实例。
```
little-cui merged pull request #1029:
URL: https://github.com/apache/servicecomb-service-center/pull/1029
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries
This is an automated email from the ASF dual-hosted git repository.
littlecui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-service-center.git
The following commit(s) were added to refs/heads/master by this push:
new 2f66380 Add
humingcheng commented on a change in pull request #1029:
URL:
https://github.com/apache/servicecomb-service-center/pull/1029#discussion_r642407055
##
File path: server/service/rbac/rbac.go
##
@@ -123,7 +122,7 @@ func initFirstTime(admin string) {
humingcheng commented on a change in pull request #1029:
URL:
https://github.com/apache/servicecomb-service-center/pull/1029#discussion_r642406916
##
File path: server/service/rbac/account_service.go
##
@@ -0,0 +1,179 @@
+/*
+ * Licensed to the Apache Software Foundation
fanjiang-2021 commented on issue #2397:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2397#issuecomment-851354713
不同的注册发现机制,可能注册的信息和发现的信息不包括上述信息的全集,可以通过组合不同的注册发现机制,提供完整的信息。 比如,可以通过 mDNS
的方式发现网络地址(endpoints)信息, 可以通过配置文件的方式,发现契约信息。
mDNS的方式有最佳实践集成demo吗?
--
This is
This is an automated email from the ASF dual-hosted git repository.
littlecui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-service-center.git
The following commit(s) were added to refs/heads/master by this push:
new 7f9ac68 role binding
little-cui merged pull request #1027:
URL: https://github.com/apache/servicecomb-service-center/pull/1027
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries
little-cui commented on issue #1030:
URL:
https://github.com/apache/servicecomb-service-center/issues/1030#issuecomment-851330883
看消费端是如何实现缓存的,我理解,应该需要定期调用/v4/default/registry/instances接口感知实例变化,实例变化包括他的instanceId、endpoint、或自定义的properties,如果做到这几点,是能判断出来实例不一样,而不是认为实例是同一个。确认下消费端是代码是否有BUG
little-cui commented on a change in pull request #1029:
URL:
https://github.com/apache/servicecomb-service-center/pull/1029#discussion_r642301223
##
File path: server/service/rbac/account_service.go
##
@@ -0,0 +1,179 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF)
tianxiaoliang commented on a change in pull request #1029:
URL:
https://github.com/apache/servicecomb-service-center/pull/1029#discussion_r642297244
##
File path: server/service/rbac/rbac.go
##
@@ -123,7 +122,7 @@ func initFirstTime(admin string) {
humingcheng commented on a change in pull request #1029:
URL:
https://github.com/apache/servicecomb-service-center/pull/1029#discussion_r642282584
##
File path: server/resource/v4/auth_resource.go
##
@@ -145,29 +124,16 @@ func (ar *AuthResource) ListAccount(w
humingcheng commented on a change in pull request #1029:
URL:
https://github.com/apache/servicecomb-service-center/pull/1029#discussion_r642282584
##
File path: server/resource/v4/auth_resource.go
##
@@ -145,29 +124,16 @@ func (ar *AuthResource) ListAccount(w
humingcheng commented on a change in pull request #1029:
URL:
https://github.com/apache/servicecomb-service-center/pull/1029#discussion_r642282584
##
File path: server/resource/v4/auth_resource.go
##
@@ -145,29 +124,16 @@ func (ar *AuthResource) ListAccount(w
little-cui commented on a change in pull request #1029:
URL:
https://github.com/apache/servicecomb-service-center/pull/1029#discussion_r642276814
##
File path: server/resource/v4/auth_resource.go
##
@@ -145,29 +124,16 @@ func (ar *AuthResource) ListAccount(w
fanjiang-2021 opened a new issue #2398:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2398
背景:
在k8s环境中,将注册中心以及提供端A和提供端B重启,
由于endpoint是由k8s随机分配的浮动IP,提供端A老的IP被另外一个提供端B占用,
此时消费端C内存中缓存了提供端A的老的IP,以及新的IP,老的IP没有通知下线,
导致消费端C调提供端A,会出现概率性调用失败
fanjiang-2021 opened a new issue #1030:
URL: https://github.com/apache/servicecomb-service-center/issues/1030
**Describe the bug**
A clear and concise description of what the bug is.
场景:
humingcheng opened a new pull request #1029:
URL: https://github.com/apache/servicecomb-service-center/pull/1029
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/SCB)
little-cui closed pull request #960:
URL: https://github.com/apache/servicecomb-service-center/pull/960
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about
little-cui closed pull request #958:
URL: https://github.com/apache/servicecomb-service-center/pull/958
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about
tianxiaoliang commented on pull request #1016:
URL:
https://github.com/apache/servicecomb-service-center/pull/1016#issuecomment-851212181
感谢贡献
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
tianxiaoliang merged pull request #1016:
URL: https://github.com/apache/servicecomb-service-center/pull/1016
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries
This is an automated email from the ASF dual-hosted git repository.
tianxiaoliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-service-center.git
The following commit(s) were added to refs/heads/master by this push:
new e97cd40
30 matches
Mail list logo