-
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
Increase the XRAY cache size #1140
Comments
Recall that we install the jfrog platform using this chart Looking into our prod jfrog.tf I find the following
And then looking at the documentation here I see the following under
so it does seem like the database portion of this is seemingly out of our hands, or at least I don't know how to increase the size there. |
CLOUD ticket 14321 |
It’s not that it isn’t managed there (in reference to looking at the jfrog tf file), it’s just the PVC already exists
Online resizing is not available today. I believe there is a preview feature but we don’t have it Make sure you wait until the pvc says waiting for pod restart before scaling back up |
Finished courtesy of Chuck |
Possibly related to #1129
When the XRAY data folder gets too full the indexer "stops" working in that it will not scan any new packages
![image](https://user-images.githubusercontent.com/23174198/171208932-745d0691-2dc2-4d7b-87f2-dfb89e1e7cd8.png)
![image](https://user-images.githubusercontent.com/23174198/171209177-bb7f096e-e70b-41b6-826c-ccee61ccc56b.png)
Example under
pypi-remote-cache/35/ad/616c27cade647c2a1513343c72c095146cf3e7a72ace6582574a334fb525/pandas-1.4.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Compared to a one that was scanned
![image](https://user-images.githubusercontent.com/23174198/171209355-f41444f1-c073-44a8-89d2-d59867e006d8.png)
The cache itself is cleaned out on a regular basis, but if there are a lot of packages being scanned then its possible for the cache to become too full.
Need to find out where and how to increase the cache size for XRAY, we may want to really increase the size here especially if AVD's end up using it.
The text was updated successfully, but these errors were encountered: