-
Notifications
You must be signed in to change notification settings - Fork 123
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
Twitter connector gets stuck not running any synclets, delaying them all #927
Comments
Log looks like this:
with no twitter synclets running for many hours |
Was a synclet actually running/stuck at the time, or was this just tolerance? |
@temas investigated this, and it seemed like the |
Something was definitely stuck. No twitter synclets had run since:
Looks like timeline is probably the one that got stuck. |
This seems to be happening with the twitter connector across a great many (but not all) of our accounts. |
So it's definitely only twitter right now, and it's not isolated to timeline, I've seen tweets do it too. Netstat has no open sockets and lsof has no interesting open files. I'm going to do another code review on the twitter paging code now. My gut is telling me it's escaping from there somehow. |
Still see this (only for contacts):
Not all accounts. My super fast and unscientific internal pattern matching pinned it to old accounts (there were about 5, 3 of which were singleton's accounts), all were on 1, 6, and 7. Can't tell which connector. We need to improve the logging there. |
of note, this isn't twitter, as twitter has friends, not contacts. Adding logging right now and will update with the results. |
This is gcontacts.
Interestingly, it seems to have more than one copy running. This seems likely to be a scheduling bug coupled with a gcontacts bug (if there was a twitter bug, it has been squashed). |
I've filed the gcontacts issue as #933. Closing this one as it's resolved. |
No description provided.
The text was updated successfully, but these errors were encountered: