This message was deleted.
# troubleshooting
s
This message was deleted.
y
I forgot to add that on our dev environment, the solution is running on a single node. This is why, we would like to use local storage in this case.
g
the deep storage needs to be shared between all servers, so if it is
local
then it does need to be on a shared filesystem
i am not sure if the operator does this or not; my guess is it probably doesn't, since it's designed to work well on multi-server environments too
i think you can fix your issue by either: • modifying your setup to point the
local
deep storage at a shared filesystem • or, using a remote deep storage like
hdfs
,
s3
, or google, azure equivalents
y
Thank you for your response. Since we are not on a multi-server environment, I thought it would work just by using the pvc storage of the Druid Historical pod. What do you mean by using a shared filesystem ? Is it a same PVC used by all Druid pods ?
g
i'm not super familiar with the k8s concepts, so i am not sure exactly how a shared PVC works exactly. if it's a single filesystem that is mounted across all pods, that would be OK
y
Thanks, we'll try to figure out how to make it works