Re: Using kafka with RESTful API

Hi, A request-response structure is more suitable for your scenario, you should still persist RESTful API rather than Kafka. 1095193...@qq.com From: Desmond Lim Date: 2019-03-19 09:52 To: users Subject: Using kafka with RESTful API Hi all, Just started using kafka yesterday and I have

Using kafka with RESTful API

Hi all, Just started using kafka yesterday and I have this question. I have a RESTful API that gets JSON data from a user (via POST) passes it to an app, the app computes the data and return it to the RESTful API and the API would display the results to the user. I'm trying to do this: The

Re: kafka latency for large message

Hi Nan, Would you consider other approaches that may actually be a more efficient solution for you? There is a slide deck Handle Large Messages In Apache Kafka . For messages this large, one of the approaches

Re: kafka latency for large message

It takes time to send that much data over the network. Why would you expect a smaller latency? On Mon, Mar 18, 2019 at 8:05 AM Nan Xu wrote: > anyone can give some suggestion? or an explanation why kafka give a big > latency for large payload. > > Thanks, > Nan > > On Thu, Mar 14, 2019 at 3:53

Re: Permanent topic

Hi Maxim, I had a quick look, it seems like that was added to the Apache Kafka documentation only in version 1.1.1, which didn't get a doc update being only a patch version, so the relevant sentence is only in the docs for 2.0 [1]. Additionally, the passage was only added to the docs of the topic

Re: Permanent topic

https://www.cloudera.com/documentation/enterprise/properties/5-13-x/topics/cm_props_cdh5110_kafka.html Mentions log.retention.ms: The maximum time before a new log segment is rolled out. If both log.retention.ms and log.retention.bytes are set, a segment is deleted when either limit is exceeded.

Permanent topic

Good time of the day, We are using kafka 1.0.1, and want to create a permanent topic. One online post suggests setting retention.ms and retention.bytes to -1. The sample below shows system accepts -1 correctly, but I don't see this documented anywhere explicitly in the official documentation.

Re: Operationalizing Zookeeper and common gotchas

Hi Eno Thanks too, this is indeed helpful Best regards Patrik > Am 18.03.2019 um 18:16 schrieb Eno Thereska : > > Hi folks, > > The team here has come up with a couple of clarifying tips for > operationalizing Zookeeper for Kafka that we found missing from the > official documentation, and

Re: Operationalizing Zookeeper and common gotchas

Eno, I found this useful, thanks. Ryanne On Mon, Mar 18, 2019, 12:16 PM Eno Thereska wrote: > Hi folks, > > The team here has come up with a couple of clarifying tips for > operationalizing Zookeeper for Kafka that we found missing from the > official documentation, and passed them along to

Operationalizing Zookeeper and common gotchas

Hi folks, The team here has come up with a couple of clarifying tips for operationalizing Zookeeper for Kafka that we found missing from the official documentation, and passed them along to share. If you find them useful, I'm thinking of putting on

Re: kafka latency for large message

anyone can give some suggestion? or an explanation why kafka give a big latency for large payload. Thanks, Nan On Thu, Mar 14, 2019 at 3:53 PM Xu, Nan wrote: > Hi, > > We are using kafka to send messages and there is less than 1% of > message is very big, close to 30M. understanding kafka

Broker deregisters from ZK, but stays alive and does not rejoin the cluster

Hi all We're running several clusters (mostly with 3 brokers) with 2.1.1 We quite regularly see the pattern that one of the 3 brokers "detaches" from ZK (the broker id is not registered anymore under /brokers/ids). We assume that the root cause for this is that the brokers are running on VMs

Re: Broker suddenly becomes unstable after upgrade to 2.1.0

Hi all On 3/13/19 9:36 AM, Joe Ammann wrote: > Hi Ankur > > On 3/13/19 3:34 AM, Ankur Rana wrote: >> Hey, >> I think this is a known issue in Kafka 2.1.0. Check this out >> https://issues.apache.org/jira/browse/KAFKA-7697 >> It has been fixed in 2.1.1. > This surely does look like our issue! I

Re: [VOTE] 2.2.0 RC2

+1 (non-binding). I used the staged binaries and run some of my tests against them. All seems to look good to me. On Sat, Mar 9, 2019 at 11:56 PM Matthias J. Sax wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for release of Apache Kafka 2.2.0. > >