Re: Review Request 50828: SAMZA-994 Fix StreamAppender to work with the refactored Job Coordinator

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/50828/#review144983 --- Ship it! Ship It! - Yi Pan (Data Infrastructure) On Aug. 5,

Re: Review Request 50619: SAMZA-963: add KV storage engine timers to help identify the issues on kv stores and also add unit test

> On Aug. 5, 2016, 6:31 p.m., Yi Pan (Data Infrastructure) wrote: > > samza-kv/src/main/scala/org/apache/samza/storage/kv/BaseKeyValueStorageEngineFactory.scala, > > line 135 > > > > > > Why do we need to add the

Re: State store changelog format

I'm reporting back my observations after enabling compression. Looks like compression is not doing anything. I'm still seeing "compression-rate-avg=1.0" and the same "record-size-avg" from JMX "kafka.producer" metrics. I did set the following: systems.kafka.producer.compression.type=snappy Am I

Re: Understand KV store restoring

Sorry, you are right. It is going through the changelog topic partition by partition, which happens sequentially. Thanks, David On Fri, Aug 5, 2016 at 1:53 PM Navina Ramesh wrote: > Hi David, > > For a given container, it should go through the entire changelog

Re: Understand KV store restoring

Hi David, For a given container, it should go through the entire changelog only for the partitions owned by the tasks in the container. Restoration should happen only once and not multiple times. What logs statements do you see that indicate that it is going through the changelog multiple times?

Understand KV store restoring

Within a given container, does the restoration process go through the changelog topic once to restore ALL stores in that container? From the logs, I have a feeling that it is going through the changelog multiple times. Can anyone confirm? Thanks, David

Re: Review Request 50619: SAMZA-963: add KV storage engine timers to help identify the issues on kv stores and also add unit test

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/50619/#review144968 --- Ship it! LGTM. Just one minor comment. Thanks!

Re: Samza yarn job - cannot bind to local host

Hey Shekar, There's currently no way to force the port or disable the JMXServer. We've seen port conflicts (fixed in 10.1) and connection issues due to VPN but no connection issue for other reasons. While googling that exception, I found a couple cases without clear resolutions, but they were

Re: Samza yarn job - cannot bind to local host

Any pointers on this please. I am completely blocked. - Shekar On Thu, Aug 4, 2016 at 5:05 PM, Shekar Tippur wrote: > This server is not connected to vpn. > > - Shekar >