My clients (producers) are combination of devices, sensors, application
hence volume of producers would be high. All I want to ensure Broker
receives data from trusted (my own) devices.
On Fri, Feb 16, 2018 at 9:33 AM, Martin Gainty wrote:
> majority of commercial entities
Hi everyone
I'm designing a control handling for my kafka stream api.
I'm would like to know any documentation or best practise that I can read.
Basically I'm creating some topics error for failed messages and retry
topics.
Any suggestions?
Thanks
It appears that kafka and/or kafka streams has gotten itself into a weird
state. My KS app is not running. I try to reset it using the reset command
line tool and I get:
ERROR: java.lang.IllegalStateException: Consumer group
'dp-consumption-aggregation-processor-staging2' is still active. Make
+1. Verified artifacts and ran quickstart. Thanks Ewen!
-Jason
On Thu, Feb 15, 2018 at 1:42 AM, Rajini Sivaram
wrote:
> +1
>
> Ran quickstart with binaries, built source and ran tests,
>
> Thank you for running the release, Ewen.
>
> Regards,
>
> Rajini
>
> On Thu, Feb
majority of commercial entities (banks/financial-houses) pass this to a CA
(certifying authority) who will be responsible for
generating X509 certificates
generating private key
generating public key
generating username (aka alias)
generating password
this depends on what type of PKI your client
Hi There,
We see spikes in the metadata request calls when a broker machine
specified in the broker list goes down i.e server not reachable. Is there a
property which can be set in the Java client to control the timeout when a
broker is not reachable and try another one in the list. We are
Any general best practice which can be followed in Kafka on this?
On Thu, Feb 15, 2018 at 9:39 PM, Jakub Scholz wrote:
> I'm afraid Kafka will not offer any help with this - at least not as far as
> I know. You have to implement it on your own.
>
> Jakub
>
> On Thu, Feb 15,
I following the Quickstart guide for v1.0.0 here -
https://kafka.apache.org/quickstart
Zookeeper starts
Kafka broker starts
I successfully create test topic
I attempt to write to the producer using the following
bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
> message 1
I'm afraid Kafka will not offer any help with this - at least not as far as
I know. You have to implement it on your own.
Jakub
On Thu, Feb 15, 2018 at 3:58 PM, Sivaprakash wrote:
> In this case how authentication keys can be maintained? If I want to change
>
In this case how authentication keys can be maintained? If I want to change
key/password for my cluster how can I change it in my clients (producers)
because they might be sitting in my remote place (sensors/mobile apps)?
On Thu, Feb 15, 2018 at 7:30 PM, Jakub Scholz wrote:
>
Yes, the clients do not connect to Zookeeper anymore. You can create a
loadbalancer which will point to all your Kafka brokers and use the address
of such loadbalancer as the "bootstrap server" in your clients. The clients
will use the loadbalancer and connect to one of the Kafka brokers and get
Hi,
Just trying to understand how Zookeeper works with Kafka in recent
versions. Document says Zookeeper need not be connected by Producer and
Subscriber.
How to assign a static IP to the whole cluster (anything like load
balancer) ? I want my producers to use only one IP or domain to publish
+1
Ran quickstart with binaries, built source and ran tests,
Thank you for running the release, Ewen.
Regards,
Rajini
On Thu, Feb 15, 2018 at 2:31 AM, Guozhang Wang wrote:
> +1
>
> Ran tests, verified web docs.
>
> On Wed, Feb 14, 2018 at 6:00 PM, Satish Duggana
13 matches
Mail list logo