dynamically changing log level on a running broker?

Hello hello, >From what I see at KAFKA-16 and KAFKA-429 , it should be possible to change log levels on a running broker process. The patches appears (to my naive eyes: I speak no Java/MBeans, and ve

Re: 0.8 producer -- many questions

I considered this as well; in my opinion, not all code will be so layered as the scala code. A topic metadata response would use the same mechanism, including the [reference]s. So in reality it's not *that* far away from BNF, but I am asking about more emphasis on layout, and revealing type/size

Re: 0.8 producer -- many questions

Jay, You're probably right about the version thing -- I tend toward the paranoid, but if support tooling is clear and easy to use, it turns out better for everybody. Especially if they are nicely versioned, and live nearby actual protocol docs :) b

Re: 0.8 producer -- many questions

First off, let me amend my previous votes: +1 for both ApiKey and ApiVersion in all responses, even @ 4 bytes. The number of bytes is insignificant, useful in the debugging and multiplex scenarios, even if the underlying service doesn't yet support it. (The protocol still can.) CorrelationId can

Re: 0.8 producer -- many questions

+1 on keeping the field for sanity checking (it's only 1 byte) +1 on each API/protocol having a singular version, ie Request+Response are a single moving version, even if one side changes w/o the other changing b

Re: 0.8 producer -- many questions

Ok. This is actually what I did in my first version of the code (the queue of outstanding requests). I merely thought that it might offer parallelism between variant request types. As you mentioned, increased parallelism is a good thing for performance, but my question was more about what is pro

Re: 0.8 producer -- many questions

I just realized something important. The BoundedByteBufferSend comment above is not in sync with my original question. I was asking about Responses -- meaning, can I multiplex off a single socket, and when reading an arbitrary response, switch on request_id to the right handler? In the blocking

Re: 0.8 producer -- many questions

Since the v0.8 protocol wire changes went in, it's time for me to fix my protocol things. One immediate question: On Tue, Nov 27, 2012 at 1:32 AM, Joel Koshy wrote: > The requestId for each request-type is written out to the wire (see > BoundedByteBufferSend) > The code I find writes a reques