Done, https://issues.apache.org/jira/browse/KAFKA-824
2013/3/25 Neha Narkhede neha.narkh...@gmail.com
On the Kafka JIRA - https://issues.apache.org/jira/browse/KAFKA
Thanks,
Neha
On Sunday, March 24, 2013, Yonghui Zhao wrote:
Sure. no problem. Where should I file the bug?
Hi Jun,
I used kafka-server-start.sh to start kafka, there is only one jvm setting
-Xmx512M“
Do you have some recommend GC setting? Usually our sever has 32GB or 64GB
RAM.
2013/3/22 Jun Rao jun...@gmail.com
A typical reason for many rebalancing is the consumer side GC. If so, you
will see
Thanks for finding those. Looks like a copy and paste issue. I've updated
the document.
Thanks,
Chris
On Sat, Mar 23, 2013 at 11:27 AM, Jonathan Hodges hodg...@gmail.com wrote:
Many thanks for contributing! The docs are very helpful. I found a couple
small possible typos. The
Hi David,
Thanks for the feedback. I've seen the example before and after in
different books/articles and it doesn't matter to me.
Anyone else want to help define a style guide or is there one I didn't see
already?
Thanks,
Chris
On Thu, Mar 21, 2013 at 7:46 PM, David Arthur mum...@gmail.com
For Kafka 0.7 in production at Linkedin, we use a heap of size 3G, new gen
256 MB, CMS collector with occupancy of 70%.
Thanks,
Neha
On Sunday, March 24, 2013, Yonghui Zhao wrote:
Hi Jun,
I used kafka-server-start.sh to start kafka, there is only one jvm setting
-Xmx512M“
Do you have some
Chris,
This looks good. One thing about partitioning. Currently, if a message
doesn't have a key, we always use the random partitioner (regardless of
what partitioner.class is set to).
Thanks,
Jun
On Thu, Mar 21, 2013 at 11:42 AM, Chris Curtin curtin.ch...@gmail.comwrote:
I published my
If you look at the description of the map method, it states:
size - The size of the region to be mapped; must be non-negative and no
greater than Integer.MAX_VALUE
-David
On 3/25/13 4:37 PM, S Ahmed wrote:
but it show's long not int?
Isn't it then Long.MAX_VALUE ?
On Mon, Mar 25, 2013 at
Hi,
We use kafka 0.7.2 and use virtual IP for producer end, the VIP tools we
are using is LVS.
Sadly, it seems not working on LVS, when the broker changes, the producer
seems not reconnect to the new broker.
So has anyone been successfully using the same VIP mode? What VIP tools are
you using?
Any suggestion on consumer side?
在 2013-3-25 下午9:49,Neha Narkhede neha.narkh...@gmail.com写道:
For Kafka 0.7 in production at Linkedin, we use a heap of size 3G, new gen
256 MB, CMS collector with occupancy of 70%.
Thanks,
Neha
On Sunday, March 24, 2013, Yonghui Zhao wrote:
Hi Jun,
I
That really depends on your consumer application's memory allocation
patterns. If it is a thin wrapper over a Kafka consumer, I would imagine
you can get away with using CMS for the tenured generation and parallel
collector for the new generation with a small heap like 1gb or so.
Thanks,
Neha
On
Thanks Neha, btw have you seen this exception. We didn't restart any
service it happens in deep night.
java.lang.RuntimeException: A broker is already registered on the path
/brokers/ids/0. This probably indicates that you either have configured a
brokerid that is already in use, or else you
You can't create the topic with the same name before deleting it first.
Thanks,
Jun
On Mon, Mar 25, 2013 at 9:58 AM, Scott Clasen sc...@heroku.com wrote:
Jun Thanks. To clarify, do you mean that clients will have cached broker
lists or some other data that will make them ignore the new
12 matches
Mail list logo