thai-op commented on issue #663:
URL: https://github.com/apache/solr-operator/issues/663#issuecomment-2021195667
> Solr needs different directories for each pod though, so I'm not exactly
sure what a shared PVC would do for you (other than to be used for backups).
From the perspective of the shared fs, the mounted dir will be different for
each pod via the usage of `subPathExpr: $(POD_NAME)`. But from the perspective
of each Solr pod, it's the same dir. For example:
```
volumes:
- name: shared-data
source:
persistentVolumeClaim:
claimName: shared-fs-pvc
defaultContainerMount:
name: shared-data
mountPath: "/solr-data"
subPathExpr: $(POD_NAME)
```
Then we can configure Solr home to be under `/solr-data` which is mounted to
`/$(POD_NAME)` under the shared FS file system. There are several benefits to
this deploy:
This is just a starting idea here to separate compute from storage for Solr.
Several cluster could be bootstrapped and mounted with a read-only PVC to
inherit all the existing data without any copy & isolate heavy write workload
from read traffic. It also allows the storage to scale horizontally without
adding new nodes (which requires a rebalance of shards) just to name a few.
Anyhow, I've prototyped a working version in my own branched that is tested
to be working internally:
https://github.com/thai-op/solr-operator/commit/80addcd4d57ee2bb9b0a961497f443b399608ad4.
If it's possible, do you might help me with shepherding / pr-reviewing it so
we can have this feature in a future Solr operator version?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
