Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuring kafka producer clients #213

Open
lftrevisan opened this issue May 18, 2016 · 4 comments
Open

Configuring kafka producer clients #213

lftrevisan opened this issue May 18, 2016 · 4 comments

Comments

@lftrevisan
Copy link

Hi folks,

We've been trying to configure a kafka cluster using kafka mesos framework and we're having some problems in order to decide how to configure our kafka java producer client.

It requires the bootstrap.servers argument that should point to a list of broker IPs for the initial metadata information but now the brokers may be running on any instance of my mesos cluster.

I understand that I can query the kafka scheduler REST API and get a list of brokers and then dynamically configure my producer client or we can also run Mesos DNS and use DNS as well.

I'd like to get some ideas how you have been configuring your producer client.

Luiz

@gondor
Copy link

gondor commented May 26, 2016

+1 Would love to see the teams thoughts on this too, going through the same process.

@joestein
Copy link
Contributor

joestein commented May 26, 2016

We have been talking about adding to the scheduler interface the bootstrap response for beta data. This way the scheduler should "talk" like a broker and be able to then have the producer get the information the scheduler wants to send for which broker partition to talk too. Its the type of things we have done in custom implementations you can do blue green with monkey patching the min broker call https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/NetworkClient.java#L352-L370 in the producer for which broker to use (current producer kafka does min requests, this makes it talk back to broker proxy in this OSS case would be scheduler).

We have been working on this https://github.com/elodina/java-mesos-util so we can support both "old" and "new" Mesos API (1.0 is coming) so maybe after that and a few other things we can get back this items (it is really near on our roadmap)

@ghughal
Copy link

ghughal commented May 26, 2016

+1 for this. We are having similar issue as well.

@steveniemitz
Copy link
Contributor

+1 also, this is a great idea!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants