-
Notifications
You must be signed in to change notification settings - Fork 89
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
SCD Traffic concurrent prober check fails on cloud deployment #1002
Comments
The check fails for the following dss image deployments (Note that the cockroach db has not been reset between runs):
Additional checks:
|
|
Successful prober tests have been run following the merge of #1004 on a similar configuration. Result:
3 runs have been performed with similar results. |
@barroco, little non-urgent question about the early locking added in #1004: is there a particular reason we do not filter out subscriptions that aren't within the time-range of interest? We seem to look for all subscriptions that cover a cell, regardless if this subscription's time boundaries overlaps with the OIR being created or mutated. As a consequence we might be locking more subscriptions than necessary: if filtering out unwanted subscriptions can be done efficiently (I assume we have the correct indices for this) we may be able to reduce contention even further? Another observation: when we do (I ran into this while looking at #814) |
Describe the bug
The prober fails when testing a cloud deployment. Failure in appended at the end of this report.
Problem has been identified when deploying the DSS on GCP using helm.
To Reproduce
interuss/monitoring:v0.3.0
Note that the test has been conducted from a local machine (based in Switzerland) and the cluster is deployed in US east region.
Stacktrace
The text was updated successfully, but these errors were encountered: