Stefano Magalini
12/27/2022, 10:48 AMRishi Rana
12/27/2022, 7:14 PMRupesh Khandelwal
12/27/2022, 9:23 PMRahul Sharma
12/28/2022, 11:18 AMVijay Narayanan
12/29/2022, 1:34 AMLinsong Wang
01/01/2023, 7:07 AMBharat Thakur
01/03/2023, 4:06 AMBharat Thakur
01/03/2023, 4:07 AMNick M
01/03/2023, 12:44 PMVijay Narayanan
01/04/2023, 4:12 AMAnand
01/04/2023, 7:57 AMkfaraz
01/04/2023, 6:06 PMAbhishek Agarwal
01/05/2023, 5:03 AMTomer Ben David
01/05/2023, 1:06 PMBharat Thakur
01/05/2023, 3:01 PMBharat Thakur
01/05/2023, 3:01 PMBharat Thakur
01/05/2023, 3:02 PMRoger Gabarit
01/06/2023, 9:42 AMBharat Thakur
01/06/2023, 11:48 AMVadim
01/06/2023, 7:48 PMbin/start-druid
script automatically starts the Druid services for you and sizes them ideally for your machine's memory and CPU capacity. Handilly you can also give it an explicit tartget for the ammount of memory to use via a -m
parameter (it defaults to 80% of total machine memory).
While this startup script was meant for newcomers to Druid to get the best experience, it has been game changer for me personally as I often rebuild Druid from master (as you can imagine). I used to always have to substitute the bundled configs with my own configs that target different deployment scenarios. Now I can put all of that behind me! I simply run bin/start-druid
or bin/start-druid -m 16g
(if I want Druid to be small) or bin/start-druid -m 32g -s broker,router,coordinator-overlord,historical,indexer,zookeeper
(if I want to play with the indexer) and it just works! No more `cp`ing my hand rolled configs.Bharat Thakur
01/07/2023, 6:35 AMBharat Thakur
01/07/2023, 6:35 AMBharat Thakur
01/07/2023, 6:35 AMAshok Kumar Ragupathi
01/09/2023, 10:23 AMAshok Kumar Ragupathi
01/09/2023, 10:23 AMAshok Kumar Ragupathi
01/09/2023, 10:24 AMAshok Kumar Ragupathi
01/09/2023, 10:24 AMVijay Narayanan
01/09/2023, 10:36 AMRahul Sharma
01/09/2023, 12:00 PMBharat Thakur
01/09/2023, 12:10 PM