spring-cloud-tencent icon indicating copy to clipboard operation
spring-cloud-tencent copied to clipboard

Spring Cloud Tencent is a Spring Cloud based Service Governance Framework provided by Tencent.

Results 65 spring-cloud-tencent issues
Sort by recently updated
recently updated
newest added

**What is the feature you want to add?** Add new `spring-cloud-tencent-docs` module **Why do you want to add this feature?** Markdown files can be directly exported to Html or pdf...

documentation

## PR Type Feature ## Describe what this PR does for and how you did. add @ConditionalOnConfigReflectEnabled annotation ## Adding the issue link (#xxx) if possible. #470 ## Note ##...

change the address of polaris config server ## PR Type ## Describe what this PR does for and how you did. ## Adding the issue link (#xxx) if possible. ##...

**What is the feature you want to add?** **Why do you want to add this feature?** **How to implement this feature?** **Additional context** Add any other context or screenshots about...

enhancement

**Describe the bug** 官方给的 polaris 地址是这个 > Console Address : http://14.116.241.63:8080/ Username: polaris Password: polaris Server Address: grpc://183.47.111.80:8091 The example addresses under spring-cloud-tencent-example all point to the experience service address...

bug
waiting for feedback

**What is the feature you want to add?** **Why do you want to add this feature?** **How to implement this feature?** **Additional context** Add any other context or screenshots about...

enhancement

**What is the feature you want to add?** 当前的北极星版本:1.6.0-2020.0.5,在服务主调其他服务接口失败后切换重试节点使用的是随机负载均衡的算法。 希望能支持以下功能:可以自定义实现类似负载均衡的算法,以及提供默认的轮询负载均衡算法、随机负载均衡算法。 **Why do you want to add this feature?** 北极星版本:1.6.0-2020.0.5 我在进行北极星和springcloud 2020版本测试(测试过程如下图):测试 主调失败重试 时有个疑问:主调方失败后重试的节点是随机取的,有可能取到同一个节点,这不太合理。因为有这么一个场景,我们k8s上的pod每次发布时都是滚动更新的,滚动更新期间有请求的流量打过来就会失败,此时不应该再在这个节点上进行重试,而是切换节点进行重试。 测试过程: 北极星注册的微服务如下,有4个节点: 主调方LoadBalancer配置如下: 调用失败重试结果: 结果呈现是:在8085端口的服务请求失败后还是重试8085端口,以及后面8083端口也是同样的情况~ **How to...

enhancement

北极星版本:1.6.0-2020.0.5 问题描述:服务正常上线后如下图,有两个节点(8084端口的节点和8085端口的节点),假设8084端口的节点发生OOM或未知故障,通过网关Gateway访问此服务时,仍会请求到8084端口这个有问题的节点。

waiting for feedback

**What is the feature you want to add?** **Why do you want to add this feature?** 如果使用refresh_context的方式实现动态配置刷新,也会实例化反射的方式的相关bean,可以看看能否不实例化。 **How to implement this feature?** 添加`@ConditionalOnConfigReflectEnabled`注解,并添加到响应的bean实例化方法上。 **Additional context** No.

enhancement

**What is the feature you want to add?** 服务注册发现支持优雅上下线。 **Why do you want to add this feature?** 最终实现参考: - 服务上线时,待服务准备完成,再注册。 - 服务下线时,先解注册,再待所有请求执行完成后,结束进程。 **How to implement this feature?** 实现代码前,需要在issue内提出方案,待讨论后再进行开发。 **Additional context**...

enhancement
help wanted
need discuss