g to parse the large xml root document and re-wrap
> each child element with a shallow clone of its parents as I iterated the
> stream.
>
> -Luke
>
>
> From: Denny Lee >
> Sent: Tuesday, June 24, 2014 10:35 AM
>
LLC
http://www.stealth.ly
Twitter: @allthingshadoop
/
On Tue, Jun 24, 2014 at 12:37 PM, Denny Lee wrote:
Hey Joe,
Yes, I have - my original plan is to do something similar to what you suggested
which was to simply push the data into HDFS / S3 and
, Jun 24, 2014 at 11:35 AM, Denny Lee wrote:
> By any chance has anyone worked with using Kafka with message sizes that
> are approximately 50MB in size? Based on from some of the previous threads
> there are probably some concerns on memory pressure due to the compression
>
By any chance has anyone worked with using Kafka with message sizes that are
approximately 50MB in size? Based on from some of the previous threads there
are probably some concerns on memory pressure due to the compression on the
broker and decompression on the consumer and a best practices on
d short of closing the
>> >process.
>> >
>> >I actually don't have access to a windows machine so it is a little
>>hard
>> >for me to test this. The question is whether there is any work around.
>>I
>> >am
>> >happy to change that met
Hey Jun,
We've been running into this issue when running perf.Performance as per
http://blog.liveramp.com/2013/04/08/kafka-0-8-producer-performance-2/.
When running it using 100K messages, it works fine on Windows with about
20-30K msg/s. But when running it with 1M messages, then the broker fail
hanks,
>
> Jun
>
>
> On Fri, Jun 28, 2013 at 12:09 AM, Denny Lee wrote:
>
> > Quick follow up - I snagged the 0.8.0-beta1-candidate1 from github but
> I'm
> > still getting the leader error issue. The good news is that it's not
> > pumping out a lot of
local for partition [foo,0] on broker 0 (kafka.server.KafkaApis)
...
On 6/27/13 11:14 PM, "Jun Rao" wrote:
>This issue was fixed in kafka-903. The fix is included in the 0.8.0-beta1
>release. Do you see the same issue in that version?
>
>Thanks,
>
>Jun
>
>
on?
>
>Thanks,
>
>Jun
>
>
>On Thu, Jun 27, 2013 at 9:45 AM, Denny Lee wrote:
>
>> Quick follow up this looks a lot like KAFKA-876
>> <https://issues.apache.org/jira/browse/KAFKA-876> so I'm trying that
>>out
>> now.
>>
>>
PI. I'll try copying it over to the VM and see if it differs.
>
> Tim
>
> Sent from my iPhone
>
>> On Jun 27, 2013, at 10:12 AM, Denny Lee wrote:
>>
>> Oh, quick follow up I created a kafka-topics.bat and ran it and noticed
>> something hinke rela
:04:17,461] INFO EventThread shut down
(org.apache.zookeeper.Clien
tCnxn)
I'm wondering why the leader and replicas have a 0 value as opposed to 1.
From: Denny Lee
Date: Thursday, June 27, 2013 9:45 AM
To: "users@kafka.apache.org"
Cc: Denny Lee
Subject: Re: Kafka 0.8 on
Quick follow up this looks a lot like KAFKA-876
<https://issues.apache.org/jira/browse/KAFKA-876> so I'm trying that out
now.
From: Denny Lee
Date: Thursday, June 27, 2013 9:10 AM
To: "users@kafka.apache.org"
Subject: Kafka 0.8 on Windows issues
While I was able to
While I was able to spin it up on OSX and Ubuntu without any issues, when
running this on Windows, I get the following error message when I execute
the consumer:
WARN
[console-consumer-8585_tardis8-1372348635138-29591e5d-leader-finder-thread],
Failed to add fetcher for [test,0] to broker id:0,ho
I have a 2011 MacBook Air (4GB, i7, 256GB SSD) and for development purposes it
works like a charm. I'm only doing simple tests (ie no perf testing) and at
least in my case, heat is pretty low. I have more issues with heat when I run
Windows on Fusion ;-)
On Jun 3, 2013, at 7:17 PM, S Ahmed w
14 matches
Mail list logo
