Hi Joe,
Many thanks for such a detailed response.
So you would have a topic called "TypeA" and then setup a consumer group
> and those consumers (if you really only needed 1 consumer set the
> partitions to 1) would get everything from the "TypeA" topic. If you had
> more event types then just
Your assumption is correct. However I was under impression that shutdown should
do rebalancing, was i wrong? What is the proper way to shutdown and allow
partition to be serve by other brokers? What is the process to recover from
this? How to avoid this and still have ability to remove servers f
I assume that "We had 6 kafka in the tier" means that you had 6 kafka
brokers.
About the exception that you see: I think that the 3 brokers you took down
were having the data for [junit2_analytics_data_log,0] and no other live
broker has the data for [junit2_analytics_data_log,0].
You could run t
We are using kafka08 beta1. We had 6 kafka in the tier. I have replication
set to 3. Then 3 servers were removed using control shutdown method. I am
getting the error bellow after that.
What went wrong during shutdown? How to recover from the error? What steps
to take in order to avoid in the futu
Hi,
This will be with Kafka 0.8. That is some good guidance, thank you. To
summarize, we can scale the # of hosts/HDs as high as we want, but we
should keep an eye on the total number of partitions being handled. We've
currently configured a default of 4 partitions per topic, so we'll watch
clo
Hey Shone,
1) Failover: unfortunately it does not implement retries on failure.
However, it does prevent further loss on those partitions. If we hit
errors while sending to a partition, then we asynchronously fetch
metadata for that topic to determine if we should send to a new leader
for that par
Thanks for the heads up Joel. We would like to try if possible (we have
ambitious timelines currently). Couple of questions though:
- how robust would you consider the failover support in the current version
- is there support for compression (Snappy and Gzip)?
Thanks in advance!
Shone Sadler
Hey Shone,
Yes this been on my plate for some time but have not had enough time
to do the open-sourcing process. We implemented a producer, and hope
to release that in a few weeks. I'll send out an email to this list
when that happens.
Joel
On Tue, Aug 6, 2013 at 9:44 AM, Shone Sadler wrote:
>
A few months ago there were discussions around a C/C++ client for Kafka .80
using non-blocking socket I/O that was being worked on by LinkedIn and may
possibly be open sourced. Has there been any additional work towards the
c++ client and open sourcing it that anyone is aware of?
Thanks,
Shone S
Could you try just setting brokerlist?
Thanks,
Jun
On Tue, Aug 6, 2013 at 5:34 AM, sphinx jiang wrote:
> Hi, I am learning kafka 0.7 this days, with a single node, :)
>
> When I run the example code, I defining the Kafka appender in my
> log4j.properties like the kafka apache quickstart page
Hi, I am learning kafka 0.7 this days, with a single node, :)
When I run the example code, I defining the Kafka appender in my
log4j.properties like the kafka apache quickstart page told.
log4j.appender.KAFKA = kafka.producer.KafkaLog4jAppender
log4j.appender.KAFKA.Host = localhost
log4j.appende
11 matches
Mail list logo
