#Is it possible to have multiple data volumes for storing images? For smaller PVs.

1 messages · Page 1 of 1 (latest)

trail mural
#

(Thank you for this amazing app!)

I run immich in a k8s cluster. Very happy.

But as my image collection grows, I continue to expand my PV. Is it possible to use multiple smaller PVs instead of just one very large PV?

Practically anytime I have a network glitch, etc the underlying storage (Longhorn) has to resync the PVs across servers. The larger it is the longer it takes for one PV. Perhaps I am wrong, but feels like ti be 'better' to add additional PVs than just expanding one massive one.

sinful vectorBOT
#

:wave: Hey @trail mural,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: I have read applicable release notes.
  3. :ballot_box_with_check: I have reviewed the FAQs for known issues.
  4. :ballot_box_with_check: I have reviewed Github for known issues.
  5. :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting.
  7. :ballot_box_with_check: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

sinful vectorBOT
worn bane
#

Tbh this sounds more of an issue with your storage setup

#

You can split volumes for the different generated files etc, but that's it

trail mural
# worn bane Tbh this sounds more of an issue with your storage setup

Perhaps actually, maybe I need to read a bit more on options within k8s. Oddly hadnt' considered that, but you are probably right :X

Or actually not sure. A PV in k8s is to give a volume/mount. So also be odd if it can have multiple smaller.

I guess it is whetehr having a 500GB PV is a concern or not in a k8s environment for your sole data store.

One idea be to shard based off age, so a new PV for each year or user.

Perhaps I am wrong to be concerned that a single PV has all the image data in terms of failure scenario an the answer is just trust my offsite backup of the images.

#

Thank you for the answer @worn bane