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

Databus on Kubernetes #95

Open
manonthegithub opened this issue Jul 19, 2023 · 3 comments
Open

Databus on Kubernetes #95

manonthegithub opened this issue Jul 19, 2023 · 3 comments

Comments

@manonthegithub
Copy link
Collaborator

Running multiple instances with mods on Kubernetes

@manonthegithub
Copy link
Collaborator Author

About the storage. I think we could use ceph (https://ceph.io/en/) or hdfs and mount them as cephfs or nfs to Kubernetes as persistent volumes that would make our data storage solution reliable and and distributed, not dependent on particular physical server. This needs testing though... Maybe for Virtuoso would still be cool to have just a physical storage (for performance reasons). I would start with ceph for experimenting.

@kurzum
Copy link
Member

kurzum commented Jul 27, 2023

Ceph.io seems cool. I found this: https://medium.com/@keecheril.jobin/integrating-docker-with-ceph-56ce6c447d1b

They disable object-map, fast-diff, deep-flatten for docker. I mean ceph.io can be mounted as a normal file system, so it might work. However, it get's much slower: https://yourcmc.ru/wiki/Ceph_performance

@manonthegithub
Copy link
Collaborator Author

I think it’s performance should be enough for writing metadata and data files… for SPARQL endpoint this may be too slow… this needs thorough testing, which is unlikely we will do atm, but at the start this should be good enough

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants