Yes I have. But it lacks detailed explanation - even the document which I
have obtained through a webinar.
Log.dirs impact, imho, is the most important and relevant item to elaborate
for such publications. And I mean, by using diagrams and details that
apache Kafka and Confluent have done so far (
Have you reviewed
https://www.confluent.io/blog/getting-started-apache-kafka-kubernetes/ as a
starting point?
On Mon, 22 Oct 2018, 18:07 M. Manna, wrote:
> Thanks a lot for your prompt answer. This is what I was expecting.
>
> So, if we had three pods where volumes are mapped as the following
>
Thanks a lot for your prompt answer. This is what I was expecting.
So, if we had three pods where volumes are mapped as the following
Pod 1 = (log.dirs=/some/directory1)
Pod 2 = (log.dirs=/some/directory2)
Pod 3 = (log.dirs=/some/directory3)
if something bad happens to Pod 3 and goes down, would
Different directories, they cannot share path. A broker will delete
everything under the log directory that it does not know about
Den mån 22 okt. 2018 kl 17:47 skrev M. Manna :
> Hello,
>
> We are thinking of rolling out Kafka on Kubernetes deployed on public cloud
> (AWS or GCP, or other). We w
Hello,
We are thinking of rolling out Kafka on Kubernetes deployed on public cloud
(AWS or GCP, or other). We were hoping if someone could provide some
suggestion or insight here.
What we are trying to understand is how logs.dir property is affected when
we run Pods in a specific worker node? if
