Hi Alex, as Jun said it depends on your use case.
Folks are doing everything under the sun now with Kafka now-a-days (which
is awesome).
You can find Kafka with Accumulo, Akka, Camel, Camus, Cassandra, Druid,
LogStash, Metrics, Samza, Spark, Storm and a whole lot more more.
There is also *a lot
Dear Kafka Users,
We are using kafka 0.8.0 is our application development. To keep message
delivery reliable we want to detect any failure while sending message. To
get high throughput we are using async producer.
As of kafka 0.8.0 async producer implementation, failure to send to message
is
Hi Guozhang,
Just a follow up question. Is one simpleconsumer instance can be shared by
multiple threads and fetch data from multiple topics and commit offsets ?
It seems all the implementation are synchronized which means it can be
shared between multiple threads ? Is my understanding correct ?
Hi Jun,
That was the problem. It was actually the Ubuntu upstart job over writing
the limit. Thank you very much for your help.
Paul Lung
On 7/9/14, 1:58 PM, Jun Rao jun...@gmail.com wrote:
Is it possible your container wrapper somehow overrides the file handler
limit?
Thanks,
Jun
On Wed,
Has someone really used : log.retention.minutes in kafka 0.8.1.1.
I have my full cluster running on 0.8.1.1 and the logs data is just not
getting cleaned up.
And I see this message in kafka server.log
...
[2014-07-10 20:49:43,786] WARN Property log.retention.minutes is not valid
Hi Michal,
The rebalance will only be triggered on consumer membership or
topic/partition changes. Once triggered it will try to finish the rebalance
for at most rebalance.max.retries times, i.e. if it fails it will wait for
rebalance.backoff.ms, and then try again until number of retries
Yes it can be shared.
Guozhang
On Thu, Jul 10, 2014 at 11:12 AM, Weide Zhang weo...@gmail.com wrote:
Hi Guozhang,
Just a follow up question. Is one simpleconsumer instance can be shared by
multiple threads and fetch data from multiple topics and commit offsets ?
It seems all the
What you are doing should work. Although you might find better results by
creating the partition assignment JSON file on your own rather than using
the move topics to brokers JSON file to generate it. Doing this yourself
will allow you to optimize the number of partition moves you are making
and
