You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be a good idea to switch the default rows_per_page attribute to something more realistic. Since requests are performed until the screen is full, loading the page on my laptop triggers about 20 requests.
This might be a long shot, but I think I understand now why we have just noticed this. Once we migrated datagrepper to OpenShift 4, all traffic was routed to the same pod, even though we had two replicas. For some reason, we have to explicitly set the annotation haproxy.router.openshift.io/balance: roundrobin on the Route to utilize both pods (behavior only seen when using TLS passthrough termination).
There appears to be some sort of DB session that yields different results for different pods.
When accessing the "Feed" link on the web UI,
/raw?rows_per_page=1&delta=127800
,some messages appear for than once.If I increase the number of
rows_per_page
to 100, for example, the issue goes away.Querying the database directly further confirms that a certain message only exists once:
The text was updated successfully, but these errors were encountered: