-
Notifications
You must be signed in to change notification settings - Fork 12
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
This resource creates too many versions #1
Comments
Hi @Rukenshia, Thanks for letting me know of this issue! Sure, I'm up for changing this, it totally makes sense. |
ghost
pushed a commit
to getoutreach/jsonnet-libs
that referenced
this issue
Jan 8, 2019
Resolves issue with metadata producing many versions olhtbr/metadata-resource#1
o-orand
added a commit
to orange-cloudfoundry/cf-ops-automation
that referenced
this issue
Apr 7, 2020
switch from swce/metadata-resource to olhtbr/metadata-resource to reduce concourse database usage. See olhtbr/metadata-resource#1
o-orand
added a commit
to orange-cloudfoundry/cf-ops-automation
that referenced
this issue
Apr 8, 2020
switch from swce/metadata-resource to olhtbr/metadata-resource to reduce concourse database usage. See olhtbr/metadata-resource#1
o-orand
added a commit
to orange-cloudfoundry/cf-ops-automation
that referenced
this issue
Apr 10, 2020
switch from swce/metadata-resource to olhtbr/metadata-resource to reduce concourse database usage. See olhtbr/metadata-resource#1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
we've recently run into an issue with your resource (and a few others that work more or less the same). The issue is that concourse, with every
check
interval, creates a new rowversioned_resource
for your resource. This means that after some time, there are a lot of rows for your resource. For your resource, we are talking 300k versions across all teams. This makes concourse reaaaally slow.To fix this problem, the
check
script always needs to return an empty array and the users need to call theput
step, which will be followed up by concourse with an implicit get step. Functionality will not really change, all the users have to do is change "get" to "put". We've done the same for our resource. Sadly, thecheck
script still runs even with theput
step, which is why I'm reaching out to you in the hopes that we can change this with you.The text was updated successfully, but these errors were encountered: