Re: Changelog cleanup.policy and segment.bytes in 0.8.0

2015-01-28 Thread Chris Riccomini
Hey Zach, > At LinkedIn, do you ever let Samza or Kafka auto-create topics? We almost always auto-create. The brokers are configured this way. We're moving to a model where we'll have a web UI, and developers will be able to create their topics manually with custom configuration. When we do that,

Re: Changelog cleanup.policy and segment.bytes in 0.8.0

2015-01-27 Thread Zach Cox
Thanks a bunch for that info, Jon! It is pure gold and helps a lot. At LinkedIn, do you ever let Samza or Kafka auto-create topics? Or do you always create them by-hand before deploying code that uses them? I understand why setting the topic config segment.bytes to smaller than 1GB is beneficial

Re: Changelog cleanup.policy and segment.bytes in 0.8.0

2015-01-26 Thread Jon Bringhurst
Hey Zach, That's correct. You probably want to look into the following topic-level configs: cleanup.policy min.cleanable.dirty.ratio segment.ms segment.bytes (we usually use the default value) Also, here's some broker configs of interest that you might want to tweak (along with the settings we

Changelog cleanup.policy and segment.bytes in 0.8.0

2015-01-26 Thread Zach Cox
Hi - in Samza 0.8.0 it seems that the Kafka topic created for a key-value store changelog does not have compaction enabled, as described in this jira: https://issues.apache.org/jira/browse/SAMZA-226 If Samza creates this changelog topic, am I correct that we then later need to run something like