Samza yarn job - cannot bind to local host

I am trying to submit a Samza job to yarn and I get a error: Exception in thread "main" java.io.IOException: Cannot bind to URL [rmi://localhost:44960/jmxrmi]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested

Re: Kafka Streams

Hi, Nick, IMHO, there are following points that differs Samza from KStreams: - Stability of local state management. Samza supports durable local state and host-affinity for faster state recovery. 0.10.1 makes further progress in host-affinity to allow a) continuous check-pointing of state store;

Re: State store changelog format

Great. Thx. On Wed, Aug 3, 2016 at 1:42 PM Jacob Maes wrote: > Hey David, > > what gets written to the changelog topic > > The changelog gets the same value as the store, which is the serialized > form of the key and value. The serdes for the store are configured with the

Re: State store changelog format

Hey David, what gets written to the changelog topic The changelog gets the same value as the store, which is the serialized form of the key and value. The serdes for the store are configured with the properties: stores.store-name.key.serde stores.store-name.msg.serde If I want to compress the

State store changelog format

I'm trying to understand what gets written to the changelog topic. Is it just the serialized value of the particular state store entry? If I want to compress the changelog topic, do I enable that from the producer? The reason I'm asking is that, we are seeing producer throughput issues and

Re: Different Serde for Store and Changelog

Hi, Nick, Thanks a lot for the input. Does it work for you if you only encrypt the value? If that works, you won't have the problem w/ the order of keys in RocksDB store. Regarding to the decryption cost, if you enable the cache store, most of the cache access is to get the deserialized objects.

Kafka Streams

There has been a lot of talk around town about Confluent's new stream processing engine, Kafka Streams. We are currently using Samza and I want to get some feedback for myself and other developers on this group list about the differences and possible advantages to using Samza when compared to