servicecomb-service-center
servicecomb-service-center copied to clipboard
apache
A standalone service center to allow services to register their instance information and to discover providers of a given service
**Describe the bug** servicecomb-java-chassis 2.x 版本 和 docker sc 的版本规则 不匹配 问题 是：docker 的 service-center版本 太低了 ``` ~ docker run servicecomb/service-center -it /bin/bash 2020-03-31T03:46:20.282Z INFO core/config.go:102 service center is running...
**Describe the bug** 使用service-center/syncer（single mode）工具同步两个service-center中的微服务/实例相关数据信息 启动第一个syncer进程无报错，启动第二个进程，在第二个进程标准输出有报错： 2020/08/06 16:08:35 [DEBUG] memberlist: Initiating push/pull sync with: 10.1.70.23:30191 2020/08/06 16:08:35 [DEBUG] memberlist: Failed to join 10.1.70.23: received invalid msgType (0), expected pushPullMsg (6)...
@little-cui It seems that no null pointer check before using variable ```resp```? https://github.com/apache/servicecomb-service-center/blob/fa4c9371ed9f46f33af3e1ccc4f7ee3ce00b767b/server/service/instance.go#L118
比如测试账号创建和角色创建，其实ut代码仅需要一份，通过控制环境变量值，再运行go test即可完成ut，但是现在是不同目录下维护各自的代码，维护成本较高
调用查询服务契约的接口返回值为{“schema”:"swagger"}，该swagger值为yaml格式  拷贝到editor.swagger.io无法正常解析  能否返回json格式的swagger 
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) filed for the change (usually before you start...
**Describe the bug** app.conf配置外置etcd三节点集群地址，当外置etcd一个节点故障时，无法连接etcd **To Reproduce** Steps to reproduce the behavior: 1. app.conf配置外置etcd三节点集群地址 2. 启动外置etcd后，让etcd出现单节点故障，但集群是可服务的 3. 启动servicecomb-service-center服务 4. 发现servicecomb无法连接etcd **Expected behavior** etcd集群正常，servicecomb应该要可以连上集群正常工作 **Platform And Runtime (please complete the following information):**...
mongo快速注册特性 对注册实例的性能有3倍左右提升 默认使用实例注册流程，添加快速注册流程，并加上开关 如果开启快速注册开关，注册实例时候直接把实例放到队列然后返回 正常场景：通过定时任务进行批量注册到mongodb, 异常场景： 1.如果mongo与sc连接断注册失败情况下，则把实例放入失败队列，并重新注册 2.如果连续3次注册失败，则熔断1000ms，等到注册成功之后再恢复 3.如果单个实例注册失败次数超过500次，则丢弃该实例，等心跳发现实例不存在，SDK重新注册
