This message was deleted.
# troubleshootings
Slackbot
03/01/2023, 1:58 AMThis message was deleted.
g
Gian Merlino
03/01/2023, 2:08 AMprobably what makes the most sense is to have multi-zone kafka (if you are using kafka for ingest) and single zone druid. typically that's what people do when collecting data from lots of different places into a single location for analytics
Gian Merlino
03/01/2023, 2:09 AMif you need multi-zone druid for DR, you can have the two druid zones read the same kafka data independently (i.e. no shared druid infra)
Gian Merlino
03/01/2023, 2:10 AMalso what @Vadim said here (https://apachedruidworkspace.slack.com/archives/C0309C9L90D/p1677635539788419)
if the above suggestion doesn't work for you, it helps to know what you are hoping to gain?
j
John Kowtko
03/01/2023, 3:28 AMAre you referring to Availability Zones? Or Regions? If the latter, then will something like Decodables work here?
b
Bharat Thakur
03/01/2023, 7:21 AM@can I have same s3 bucket for multiple independent Druid
j
John Kowtko
03/02/2023, 3:19 AMAccording to the documentation, if you specify a different druid.storage.baseKey value for each cluster, then the files in the same S3 bucket will be kept separate from each other.
ref: https://druid.apache.org/docs/latest/development/extensions-core/s3.html#deep-storage
I do not know if there are any other common files that might conflict if multiple clusters tried to use the same S3 bucket ... but the docs do not mention any restrictions here.