-
Notifications
You must be signed in to change notification settings - Fork 9
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
proxy not syncing latest upstream versions #11
Comments
Still an issue. I enabled the debug log but nothing suspicious. Can someone help here? I dig a bit in the logs and saw that the following event
The next time the replication is triggered the index get not downloaded maybe this is a trace |
maybe something like #3 (comment) I tried to set the |
ok, this issue is on our agenda now. |
JFI i did some tests and changed the following parameter --- a/registry/manifest/charts.go
+++ b/registry/manifest/charts.go
@@ -171,7 +171,7 @@ func (m *Manifests) GetIndex(repoURLPath string) (*repo.IndexFile, error) {
// cache error too to avoid external resource exhausting
ttl = m.config.IndexErrorCacheTTl
}
- m.cache.SetWithTTL(repoURLPath, res, 1000, ttl)
+ m.cache.SetWithTTL(repoURLPath, res, 100000, ttl)
return res.c, res.err
}
@@ -239,7 +239,7 @@ func (m *Manifests) getIndexBytes(url string) ([]byte, error) {
// cache error too to avoid external resource exhausting
ttl = m.config.IndexErrorCacheTTl
}
- m.cache.SetWithTTL(url, res, 1000, ttl)
+ m.cache.SetWithTTL(url, res, 100000, ttl)
return res.c, res.err
} now the upstream index.yaml get downloaded every time the replication within harbor is triggered |
We have an odd issue.
After some time of running the proxy is not syncing the latest upstream version and just provide the cached versions.
When a manual pod restart is triggered the sync will work for some time again.
Example: grafana chart
harbor.log
latest upstream is
7.3.7
This happens several times with different charts now.
Any suggestion what is happen here and how to fix it?
The text was updated successfully, but these errors were encountered: