This message was deleted.
# general
s
This message was deleted.
g
I would recommend updating to Druid 25 and using the
bin/start-druid
script it sets these properties automatically based on available memory and CPU on your server more info— https://druid.apache.org/docs/latest/operations/single-server.html
a
ok
Gian, actually so far my understanding is since I launched (installed) using single-server-small i.e. ./bin/start-single-server-small whether it had hard limit / restriction to the described resource sizing i.e. 8 cpu and 64 gb, eventhough I would add resource in server (more cpu / ram / etc...) and do changes in druid single-server/small config runtime properties ? !!
g
the sized configs
small
,
medium
, etc are just starting points for various common server sizes
you can edit them as you like
a
So I can simply add resources and change the properties and still I can run / launch the druid using single-server-small ?
g
yep that is fine.
a
oh ok... great. Let me try out then
g
however, I would suggest that the newer
bin/start-druid
script is even simpler
a
Am currently facing some Query performance issue
oh... once after stop the druid service (of small) and while start again i can use bin/start-druid ?
inspite the server config and druid config properties?
s
Hi @Ashok Kumar Ragupathi you can find more information on Single Server deployment using bin/start-druid here: https://druid.apache.org/docs/latest/operations/single-server.html
This is only available from Druid version 25 onwards
It is quite useful to automatically configure your single server deployment
a
oh... ok
Thanks Saydul
s
You are welcome 🙂
You can also do this in your current version but you will have to manually update the configurations yourself.
bin/start-druid makes it a lot easier and automatic
a
having druid 25, a doubt, If stop the current druid service which launched using single-server-small and start with using bin/start-druid still the log files, data-set path are considered same
oh fine.
s
There are 2 different ways that you can approach it. You can update your existing druid version to 25. Once you upgrade, you will have bin/start-druid available. The other way is to create a separate cluster in parallel running Druid 25, migrate everything in this new cluster, test everything and then move everything over to the new cluster.
If you are using the default bin/start script, then most of the information should be in var directory. You can just copy it across
I have to check it a bit to confirm
m
Is there a way to use the bin/start-druid script also for docker deployment? I have followed the official guide for druid deployment using docker and I had to manually set lots of conf on the environment file
s
@Karan Kumar should be able to answer this better. I am not sure to be honest. An easy way to achieve this if I had to do it will be to use the bin/start-druid script to generate all the relevant config files and then update your docker config using those.
a
@Ashok Kumar Ragupathi Scaling druid clusters vertically on the basis of cpu, mem and storage is supported in the druid operator.
💯 1
a
Ok I will check Adheip thank you and thank you all