-
Notifications
You must be signed in to change notification settings - Fork 35
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
Investigate consistency issue between /latest and /next/10 #117
Comments
Caught it in the act! Here's the Jersey debug info. You can see "next/100" returns 2 URLS, but "latest" gives back an older result. Mar 12, 2015 12:54:22 PM com.sun.jersey.api.client.filter.LoggingFilter log Mar 12, 2015 12:54:23 PM com.sun.jersey.api.client.filter.LoggingFilter log Mar 12, 2015 12:54:23 PM com.sun.jersey.api.client.filter.LoggingFilter log Last uri: http://hub-v2.svc.staging/channel/FlexFlightHistoryReplicatedHubV1Staging/2015/03/12/19/54/21/817/2872372 |
Yes, we can also recreate, and are debugging now :) |
Our test against staging data, which could reproduce the issue 5 times per minute, has been running for 5 minutes with no issues. |
In a replicated channel, @chriskessel has found the following
1 - call /next/10 near the head of the channel
2 - record the last item
3 - call /latest
4 - latest returns an item previous to step 2
This happens infrequently, ~once in 50 attempts.
The text was updated successfully, but these errors were encountered: