-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
goc profile耗时很长 #155
Comments
指定服务名字清理时,如果服务已经掉线了,也会报错 goc clear --service=xxx {"error":"Post "http://172.16.71.81:8899/v1/cover/clear\": dial tcp 172.16.71.81:8899: connect: no route to host"}% |
服务端可以自动清理不在线的address吗 |
这个是说遍历一遍服务消耗的时间很长?(PS: 是否尝试了这个命令
删除服务,用 |
怎样的情况下才能判断服务"不在线"呢?我担心有误伤。 |
我也遇到了相同的问题,在容器实践过程中这是非常常见的问题,以下是我处理的方式 Line 182 in 60a18d3
在这行代码下面增加了一下的处理方式,并将 err := s.Store.Remove(addr)
if err != nil {
c.JSON(http.StatusExpectationFailed, gin.H{"error": err.Error()})
return
}
fmt.Fprintf(c.Writer, "Remove service %s from the center.\n", addr) 这样就可以在 |
PR #163 当已经修复了这个问题,先关闭。 |
我怎么觉得这个并没有修复问题呢?k8s部署的服务,无效的address越来越多 |
当有很多服务注册在goc server上面,服务被销毁后,获取覆盖率文件耗时很长,如果不手动清理,注册的服务会越来越多,耗时也越来越长。 有参数可以设置跟客服端的请求超时不
The text was updated successfully, but these errors were encountered: