I ran these same tests with Java 9 runtime today and have updated the
blog to include these numbers[1]. I'm pasting the summary for Java 9 here:
- Both for producer and consumer, there's a *drastic improvement in the
JRE shipped SSLEngine numbers, in almost all metrics, in Java 9 as
compared t
I think "CLIENT" is just an example. The default for
listener.security.protocol.map doesn't have it. If you look at the KIP link
in my email there's a more complete example:
listener.security.protocol.map=CLIENT:SASL_PLAINTEXT,REPLICATION:PLAINTEXT,INTERNAL_PLAINTEXT:PLAINTEXT,INTERNAL_SASL:SASL_P
Matt is right. KIP-150 did not make it to 1.0.0. So it may need to wait for
the next minor release (1.1.0).
Guozhang
On Fri, Nov 10, 2017 at 10:25 AM, Matt Farmer wrote:
> The JIRA ticket for its implementation still appears to be open, so I'd
> guess it's not in 1.0
>
> On Fri, Nov 10, 2017 a
Resending to include kafka-clients.
On Sat, Nov 11, 2017 at 12:37 AM, Rajini Sivaram
wrote:
> Hello Kafka users, developers and client-developers,
>
>
> This is the first candidate for release of Apache Kafka 0.11.0.2.
>
>
> This is a bug fix release and it includes fixes and improvements from 1
Hello Kafka users, developers and client-developers,
This is the first candidate for release of Apache Kafka 0.11.0.2.
This is a bug fix release and it includes fixes and improvements from 16 JIRAs,
including a few critical bugs.
Release notes for the 0.11.0.2 release:
http://home.apache.org
Yep I'm familiar with that. Just curious where it's documented that, for
instance, the CLIENT listener is for client connections.
On Fri, Nov 10, 2017, 12:08 PM Kaufman Ng wrote:
> This is related to another config "listener.security.protocol.map" (since
> version 0.10.2.0). The CLIENT, PLAINTEX
Messages that don't find a join partner are dropped.
For each incoming message, we do the following:
1. insert it into it's window store
2. lookup other window store for matching record
a) if matching records are found, compute join and emit
Note, that we maintain all records in the window
The JIRA ticket for its implementation still appears to be open, so I'd
guess it's not in 1.0
On Fri, Nov 10, 2017 at 12:28 PM Artur Mrozowski wrote:
> Hi,
> I have a question about KIP-150. Has that functionality been released in
> version 1.0 or is it planned for version 1.1?
>
> Here it says
Hi,
I have a question about KIP-150. Has that functionality been released in
version 1.0 or is it planned for version 1.1?
Here it says 1.1
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Streams
but in this blog post it seems to be part of 1.0.
https://www.confluent.io/blog/apache-kafka
This is related to another config "listener.security.protocol.map" (since
version 0.10.2.0). The CLIENT, PLAINTEXT, etc are defined as a
name-protocol mapping. So what you have in the listeners property (e.g.
CLIENT) must have an entry in the protocol map which determines which
protocol to use (e.g
Thank you very much, Stanislav,
We managed to fix it by deleting everything from kafka data dir and
zookeeper data dir.
Regards,
Vitaliy.
On Fri, Nov 10, 2017 at 5:41 PM, Stas Chizhov wrote:
> Hi, it looks like https://issues.apache.org/jira/browse/KAFKA-5970. Try
> restarting broker 1.
>
> Bes
I've been working with Kafka broker listeners and I'm curious is there
any documentation that explains what all of them apply to? Such as
CLIENT, PLAINTEXT, SASL/SSL, etc. I see the encryption part of the
documentation, but is it just inferred what these listeners apply to?
Thank you in advance!
Hi, it looks like https://issues.apache.org/jira/browse/KAFKA-5970. Try
restarting broker 1.
Best regards,
Stanislav.
2017-11-10 14:00 GMT+01:00 Vitaliy Semochkin :
> Hi,
>
> I have a cluster with 3 brokers (0.11)
> when I create a topic with min.insync.replicas=2 and replication-factor 2
> I se
Hi,
I have a cluster with 3 brokers (0.11)
when I create a topic with min.insync.replicas=2 and replication-factor 2
I see number of insync replicats in the created topic is less than
min.insync.replicas.
Why some partitions have less than 2 in sync repicas? How to prevent it?
Here is the comman
Hi Ranjit, it sounds like you might want to use a global table for this.
You can use StreamsBuilder#globalTable(String, Materialized) to create the
global table. You could do something like:
KeyValueBytesStoreSupplier supplier =
Stores.inMemoryKeyValueStore("global-store");
Materialized>
materiali
Hello there!
I am newbie in the world of Apache Kafka and I have just implemented a
standalone cluster of Kafka. I also tested it by running one producer
process and 2 consumer processes and no issues were found.
However, I would just like to know in which directory in the
LocalFileSystem the data
Hi Guozhang,
Thanks for the information.
My requirement is some thing like this.
1. i want to read the data from one topic (which is continuously feeding),
so i though of using the kafka streams with threads
2. want to store the data in one in memory data base (not the local data
store per threa
17 matches
Mail list logo