BTW, where exactly will the broker be writing these messages? Is it in a
/tmp folder?
On Tue, Dec 11, 2012 at 12:02 AM, S Ahmed wrote:
> Neha,
>
> But what do I need to start before running the tests, I tried to run the
> test "testAsyncSendCanCorrectlyFailWithTimeout" but I got this:
>
> 2012
Neha,
But what do I need to start before running the tests, I tried to run the
test "testAsyncSendCanCorrectlyFailWithTimeout" but I got this:
2012-12-11 00:01:08,974] WARN EndOfStreamException: Unable to read
additional data from client sessionid 0x13b8856456a0002, likely client has
closed socke
You can take a look at one of the producer tests and attach
breakpoints in the code. Ensure you pick the Debug Test instead of Run
Test option.
Thanks,
Neha
On Mon, Dec 10, 2012 at 7:31 PM, S Ahmed wrote:
> Hi,
>
> So I followed the instructions from here:
> https://cwiki.apache.org/confluence/d
Hey Otis,
Not sure if you mean write up the protocol or write up more detailed
release notes and deployment steps. The protocol is documented here:
https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol
We will write up migration steps as we get closer to a stable release
Hi,
Thanks Neha.
> We made protocol changes up until last Friday, so I would wait for
> another few weeks before deploying 0.8 in production, if you'd like to
> avoid incompatible releases. However, upgrading from 0.7.2 to 0.8 is
> also backwards incompatible and will require careful deployment
>
Most sites wouldn't be able to pre-aggregate--you need to report things
like uniques that require tracking and storing line items.
We use 30 seconds or 200 events as our threshold, though there is nothing
particularly good or bad about those settings.
-Jay
On Mon, Dec 10, 2012 at 10:51 AM, S Ah
Ok just looking at the code, seems like you could even create a new
implementation and somehow rollout the page views potentially (if that is
possible in the use case) before sending them over the wire.
e.g. maybe you can just increment the couter to 2 instead of sending 2 line
items.
The key is
I'll try that out. Thanks!
From: Jun Rao [jun...@gmail.com]
Sent: Monday, December 10, 2012 1:04 PM
To: users@kafka.apache.org
Subject: Re: Logging which broker a message was sent to
So, you are using Producer, not SyncProducer. Assuming that you are usin
So, you are using Producer, not SyncProducer. Assuming that you are using
DefaultEventHandler, there is a trace level logging that tells you which
broker a request is sent to.
Thanks,
Jun
On Mon, Dec 10, 2012 at 8:10 AM, Sybrandy, Casey <
casey.sybra...@six3systems.com> wrote:
> Is it at least
If you're using the zkCli.sh, something like this will create the
namespace:
[zk: localhost:12913(CONNECTED) 1] create /namespace ''
Created /namespace
If you're using another interface, the actual command may vary.
--
Dave DeMaagd
ddema...@linkedin.com | 818 262 7958
(casey.sybra...@six3syst
Is it at least possible to see which broker a message is sent to? I'm using a
Zookeeper based producer and we have multiple brokers in our environment. If I
can tell which broker a message is sent to, that would be a big help.
From: Jun Rao [jun...@gmai
If you use -1 (ie, a random partition) as the partition #, there is no easy
way to know which partition that the broker picks. However, you can
explicitly specify the partition # in the request itself.
Thanks,
Jun
On Mon, Dec 10, 2012 at 7:26 AM, Sybrandy, Casey <
casey.sybra...@six3systems.com>
A while back I experimented with this and stunnel worked pretty well for this.
Granted, I only did some basic work with it, but it looked promising.
From: Jay Kreps [jay.kr...@gmail.com]
Sent: Friday, December 07, 2012 5:58 PM
To: users@kafka.apache.org
S
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
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
Apologies for not responding sooner. My mail client must have been
malfunctioning at the time as I never saw your responses until today.
As for the error, it looks like it's a bug on my part that just didn't click
until I read Jim's responses. I have a config file that I specify the options
i
16 matches
Mail list logo