I would say you will get that 5th message in the next request.
I don't believe under any circumstance a Kafka broker will send or receive
a partial message.
On Feb 24, 2018 10:52 AM, "adrien ruffie" wrote:
> Hello,
>
>
> I have found this description in only documentation (without taking into
>
Hello!
This is a very general question but I was wondering if anyone knows whether
or not the Kafka brokers need to do any additional work to receive/respond
to requests coming in from older clients.
Even though newer brokers support older clients, is there any additional
processing time that can
or submitting a PR:
>
> https://cwiki.apache.org/confluence/display/KAFKA/
> Contributing+Code+Changes#ContributingCodeChanges-PullRequest
>
>
> I have also added you to contributor list so you can assign to yourself
> now.
>
>
> Guozhang
>
> On Sun, Dec 3, 2017 at 8
Hello,
I created a JIRA (KAFKA-6301) for a minor change to the documentation but
it doesn't seem like I can assign the ticket to myself. Can someone help me
out?
I'm also trying to commit and push the change to the Kafka repository but
I'm getting the following error:
remote: Permission to apach
Unless you're experiencing any connection issues then I would say this is a
benign warning message.
Essentially what it's saying here is that the connection was closed (broken
pipe) before it (wherever you're getting the log from) was able to send the
last close_notify message. When one party deci
it was the reason I've
> asked how Kafka is supposed to be managed.
>
> I believe managing small-ish cluster with 3-5, maybe dozen nodes is doable
> with scripts. But what happens on the scale betoubd that?
>
> --
> Roman
>
> On Fri, May 26, 2017 at 4:19 PM Waleed Fatee
Hi Roman,
I have not heard of an automated way to do this. You have to manually
reassign partitions from the Kafka broker you're planning on removing from
the cluster. Have a look at the section "decommissioning brokers" in the
documentation:
https://kafka.apache.org/documentation/#basic_ops_decom
sent out ("Question with
regards to KAFKA-3166"). I would be curious to know your thoughts on it.
Regards,
Waleed Fateem
On Thu, May 25, 2017 at 8:49 AM, Kaufman Ng wrote:
> Ismael also wrote this security blog post about Kafka security. Hope you
> find it useful:
> https
here it would have protected the Kafka server from this scenario.
Should this be a concern or "all bets are off" since the authentication
mechanism has been compromised in the first place?
Just wanted to get some thoughts on this.
Regards,
Waleed Fateem
For completion, I saw Ismael Juma post an answer which contains the
information I was looking for:
http://comments.gmane.org/gmane.comp.apache.kafka.user/15140
SASL_SSL -> authentication using SASL AND connection is encrypted using
SSL.
On Wed, May 24, 2017 at 7:37 PM, Waleed Fateem
wr
Hello!
I'm not very clear on the behavior that we should expect when we configure
Kafka to use the protocol SASL_SSL.
Is SASL or SSL mutually exclusive here or can I authenticate with SASL and
use SSL for encryption?
If the latter is true, then is it correct to assume that encryption will
take p
11 matches
Mail list logo