We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
描述bug Dubbo框架2.x服务发现采取subcribe-watch机制,只会在rpc框架启动之初调用一次polaris获取服务发现的全量数据,在此之后如果这些服务发现的数据默认24小时内无变化,便会触发cache删除机制,cache删除的同时会删除掉服务监听事件的Task,从而导致consumer失去对正在调用的provder所属北极星服务的事件监听。 目前发现该过程对如下场景均有不同程度的影响: 1、consumer内部对应的provier所属北极星服务过期之后,重启/升级provider,consumer会调用到该provider对应ip:port未启动的接口上,导致业务报错
The text was updated successfully, but these errors were encountered:
No branches or pull requests
描述bug
Dubbo框架2.x服务发现采取subcribe-watch机制,只会在rpc框架启动之初调用一次polaris获取服务发现的全量数据,在此之后如果这些服务发现的数据默认24小时内无变化,便会触发cache删除机制,cache删除的同时会删除掉服务监听事件的Task,从而导致consumer失去对正在调用的provder所属北极星服务的事件监听。
目前发现该过程对如下场景均有不同程度的影响:
1、consumer内部对应的provier所属北极星服务过期之后,重启/升级provider,consumer会调用到该provider对应ip:port未启动的接口上,导致业务报错
The text was updated successfully, but these errors were encountered: