least, I think this would have allowed a clean and
automatic recovery. Has this idea been considered before? Does it have
fatal flaws?
Thanks,
--
Jack Foy
cluster B
- Producers gradually migrate from A to B
We've found the following, which seems to suggest no, but doesn't
address the point directly:
http://events.linuxfoundation.org/sites/events/files/slides/Kafka%20At%20Scale.pdf
--
Jack Foy
r={immutableInfo=true,
interfaceClassName=com.yammer.metrics.reporting.JmxReporter$GaugeMBean,
mxbean=false}]
We can work around this by using asInstanceOf[Long], but that usually indicates
we're doing something wrong.
Am I missing something here? I would expect types like Scala Long to be
preserved across JMX.
--
Jack Foy mailto:j...@whitepages.com>>
n SSDs and 2) Turning sync on every write off
> (zookeeper.forceSync). I'm not sure if #2 negatively affected the
> consistency of the zookeeper data ever but it did help with speeding up the
> rebalancing.
OK, thanks very much for the guidance.
--
Jack Foy
workable strategy with high-level consumers? Can we actually deploy a
consumer group with this many consumers and partitions?
We see throughput of more than 500,000 messages per second with our 512
consumers, but we need greater parallelism to meet our performance needs.
--
Jack Foy
