This message was deleted.
# troubleshooting
s
This message was deleted.
👍 2
d
I have to note, this only works if you put hostname inside druid.host. Don’t put IP addresses.
f
@Didip Kerabat This is really cool. Thanks for your work. Can I ask why we need to have two clusters to achieve 0 downtime environment? Per the Druid document, it is suggesting to use rolling updates.
d
@Frank Cao This stems from the need to roll upgrade AWS EKS versions. Druid has never been able to tolerate EKS rolling upgrade (Druid 25 dealt with it much better thanks to the new Apache Curator library), but it wasn’t perfect. For some of our apps, they are P0 mission critical. We must absolutely achieve 0 downtime.
One more thing, you need to make your historical tiers looked like the following so that you can replicate between 2 clusters. This cannot be achieved using the UI. You have to submit directly using the API.