-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
如何保证judge模块的高可用? #1
Comments
judge 所在的机器,如果坏掉了,是需要人工介入处理的 所以,这块就没有做transfer对 judge的自动摘除。 后续可以考虑下如何更好的优化 |
Closed
salixleaf
pushed a commit
to falconbaby/falcon-plus
that referenced
this issue
May 19, 2017
Merge pull request open-falcon#11 from oiooj/master
salixleaf
pushed a commit
to falconbaby/falcon-plus
that referenced
this issue
May 19, 2017
add model.nodata
salixleaf
pushed a commit
to falconbaby/falcon-plus
that referenced
this issue
May 19, 2017
add practise in readme,add file git.go, turn off blocking, add proc/config/,add faq
salixleaf
pushed a commit
to falconbaby/falcon-plus
that referenced
this issue
May 19, 2017
add pfc, look ok
Closed
Closed
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
我看了一下transfer的代码,发现transfer对judge模块的一致性哈希表是不会动态变化的,judge的状态只是内存中缓存的11分钟数据,设计时为什么不考虑让transfer能够做到自动剔除不可用的judge呢?
The text was updated successfully, but these errors were encountered: