Sphinx更新属性失败
我需要知道如果请求来自并发,我们如何解决更新属性失败的问题?实际上,我们在负载均衡器中使用 10 个 sphinx 服务器,如果尝试使用更新属性更新 10 个 sphinx 服务器中的某些即时更新,则其失败的次数将超过 10 个服务器之一(可能是 4、5 或 6 个 sphinx 服务器) 。所以在应用程序方面,我们无法正确显示我们立即更新的状态,因为它来自负载均衡器。此类问题如何解决?
请帮助我们解决此问题或分享您的意见。 sphinx中的RT指数怎么样?
I need to know how we can resolve the update attribute failure if request comes from concurrently?. Actually we are using 10 sphinx server in load balancer and if try to update the some instant update in 10 sphinx server using update attribute, its getting failure any more than one of the 10 servers (it may be 4 or 5 or 6 sphinx server). So In application side, we cant able to show the status correctly which we have updated instantly, because its comes from load balancer. How can resolve this kind of issues?.
Please help us to close this issue or share your input.
What about RT index in sphinx?.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您可以使用实时索引来替代 main+delta 索引创建方法。它们有助于减少服务器工作负载并简化索引更新。
但如果您想使用它们,则必须记住以下几点:
You could use real-time indexes as a replacement of the main+delta index creation method. They are helpful to reduce server workload and simplify index updating.
But you have to keep in mind following points, if you want to use them: