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
After the new node is added, the data on the old node is not migrated. If the new node is removed soon, the data will be inconsistent
The text was updated successfully, but these errors were encountered:
Consider adding a Delete API?
Sorry, something went wrong.
这个项目只是一个玩具项目。在实际生产中,一份数据不可能只缓存在一个节点上,在geek-cache中,访问节点的请求会经过一致性哈希落到哈希环中的某个节点上,当这个节点宕机,缓存在该节点的数据将失效,新的请求经过映射后会映射到其后的一个节点之上。我们可以考虑将一致性哈希做在proxy层,将geek-cache再抽象化,哈希环中的每个节点都是一个集群,通过QuorumNWR算法来实现自定义的一致性,当然,这只是个idea,具体的实现还需要进一步讨论。
解决基本一致性问题,缓存key与哈希值,监听虚拟节点通知,对自有key进行管理。 @leaf-dawn
leaf-dawn
No branches or pull requests
After the new node is added, the data on the old node is not migrated. If the new node is removed soon, the data will be inconsistent
The text was updated successfully, but these errors were encountered: