This message was deleted.
# troubleshooting
s
This message was deleted.
t
Okay, I think I’ve just found how to configure it, using :
druid.processing.tmpDir
l
Alternatively it can be specified by
java.io.tmpDir
(which has a lower precedence however)
t
Thanks @Laksh Singla for pointing this out
It looks like the priority of
druid.processing.tmpDir
over
java.io.tmpDir
is not honoured. In my
jvm.config
I have
-<http://Djava.io|Djava.io>.tmpdir=var/tmp
and in my
runtimes.properties
I have
/opt/druid/var/druid/processing
. Yet,
/opt/druid/var/druid/processing
does not even exist and I have some files in
/opt/druid/var/tmp
The safest way for now would be to set the same path on both configuration params?
l
Thanks for reporting this, it definitely seems like a bug. Can you please share the startup properties from the logs. They should be present at the starting (and if not, https://druid.apache.org/docs/latest/configuration/index.html#startup-logging should be enabled).
Beware to mask any secrets and passwords before sharing the logs 😅
g
Important to note: the
druid.processing.tmpDir
is only for the spill-to-disk that happens during queries Other stuff will still potentially use other tmpdirs. It's like this because you may want to use different tmpdirs for different things. If you do want to change them all at once, it's best to change
java.io.tmpDir
, which is the default for all tmp dirs
t
Thanks Gian.