Skip to content
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

Closed
Jose-Matsuda opened this issue May 31, 2022 · 4 comments
Closed

Increase the XRAY cache size #1140

Jose-Matsuda opened this issue May 31, 2022 · 4 comments
Assignees
Labels
kind/bug Something isn't working size/S ~1 day

Comments

@Jose-Matsuda
Copy link
Contributor

Jose-Matsuda commented May 31, 2022

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
Example under pypi-remote-cache/35/ad/616c27cade647c2a1513343c72c095146cf3e7a72ace6582574a334fb525/pandas-1.4.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
image

Compared to a one that was scanned
image

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.

@Jose-Matsuda Jose-Matsuda added kind/bug Something isn't working size/S ~1 day labels May 31, 2022
@Jose-Matsuda Jose-Matsuda self-assigned this May 31, 2022
@Jose-Matsuda
Copy link
Contributor Author

Recall that we install the jfrog platform using this chart

Looking into our prod jfrog.tf I find the following

xray:
  enabled: true
  database:
    user: xray@...
    actualUsername: xray
    password: '...'

And then looking at the documentation here I see the following under database

## Database Configuration
  ## PostgreSQL database used by all xray services
  database:
    #type: postgresql
    #driver: org.postgresql.Driver
    #url: "postgres://<your db url, for example: localhost:5432>/xraydb?sslmode=disable"
    #username: xray
    #password: xray
    ## Some managed databases like Azure have a different username for accessing the database than the actual one inside the database
    ## for Azure managed postgres for example username will be xray@mycompany and the actualUsername will be xray
    #actualUsername: ""

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.

@Jose-Matsuda
Copy link
Contributor Author

CLOUD ticket 14321

@Jose-Matsuda
Copy link
Contributor Author

Jose-Matsuda commented Jun 13, 2022

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

  1. Scale down xray statefulset
  2. Change PVC size with kubectl edit (edited)
  3. Scale back up

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

https://carlos.mendible.com/2021/11/15/aks-resize-private-volume-claim-to-expand-a-managed-premium-disk/

@Jose-Matsuda
Copy link
Contributor Author

Finished courtesy of Chuck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working size/S ~1 day
Projects
None yet
Development

No branches or pull requests

2 participants