-
Notifications
You must be signed in to change notification settings - Fork 8
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
instances not up to date status list #13
Comments
It looks like the issue was related to the two servers have clocks out by 3 min. So one server was refusing to show future updates. Perhaps the code could be made more robust by when showing the latest updates, to include future updates to handle clock problems? |
On 18/06/14 13:26, Dylan Jay wrote:
Thanks for the bug report, Dylan. I checked the code but there's no filter that excludes future status More probably this has to do with the in-memory batch queing mechanism It's difficult to find and fix these kind of Heisenbugs without a Anything you can add to diagnose this would be helpful. If you see this Please don't do that if your traffic exceeds 20 statusupdate insertions :*CU#
|
Syncing the time of the servers solved the problem. I don't see how it |
We are using load-balancing across instances with 2 threads each, 4 on each server. I'm getting some strange errors with status updates not appearing. Either directly after entering a status or if refreshing the microblog page several times as it round-robins through the various zope instances. Eventually the instances all get up to date but it takes a few minutes.
The text was updated successfully, but these errors were encountered: