Hi Tao,
Yes, the issue that ErrorLoggingCallback keeps value as local variable is
known for a while and we probably should fix it as the value is not used
except logging the its size. Can you open a ticket and maybe also submit a
patch?
For unreachable objects I don¹t think it is memory leak. As
It took a little while for this to post (aligning with company PR and all),
but there's a detailed description of what Burrow is on the LinkedIn
Engineering Blog now:
http://engineering.linkedin.com/apache-kafka/burrow-kafka-consumer-monitoring-reinvented
-Todd
On Thu, Jun 4, 2015 at 6:43 PM, T
Yeah, it's definitely not a standard CAS, but it feels like the right
fit for the commit log abstraction -- CAS on a 'current value' does
seem a bit too key-value-store-ish for Kafka to support natively.
I tried to avoid referring to the check-offset-before-publish
functionality as a CAS in the ti