Re: No samza consumer group found

Hi David we also have this monitoring requirement one way I can think of is periodically reading the latest checkpoint information from the corresponding check_point topic, and then compare it with the topic offset. it's not that straight forward comparing to existing tools such as yours, and re

Re: No samza consumer group found

I asked simply because I would like to monitor the topic consumed by our samza job using tools like this: https://github.com/quantifind/KafkaOffsetMonitor On Tue, Mar 15, 2016 at 9:13 PM, Jagadish Venkatraman < jagadish1...@gmail.com> wrote: > Hi David, > > Samza is using the simple consumer -

Re: Review Request 44405: SAMZA-882 - Detect partition count changes in input streams

> On March 14, 2016, 11:46 p.m., Yi Pan (Data Infrastructure) wrote: > > samza-core/src/main/scala/org/apache/samza/system/StreamMetadataCache.scala, > > line 101 > > > > > > I am a bit confused here. I thought that

Re: No samza consumer group found

Hi David, Samza is using the simple consumer - I'm not aware of a notion of group id. Others will comment on that. As far as I know, the client id for a particular consumer instance is defined by a combination of the job name, the current timestamp and a sequence number. val clientId = KafkaUtil

Re: Review Request 44405: SAMZA-882 - Detect partition count changes in input streams

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44405/ --- (Updated March 16, 2016, 4:09 a.m.) Review request for samza, Boris Shkolnik, J

No samza consumer group found

Our samza job is consuming from a Kafka topic. AFAIU, samza will auto assign the job a consumer group id and client id. However, I'm not able to see that showing up under zookeeper. Am I missing something?

Re: Samza @ ApacheCon BigData 2015

Hi, Renato, Did you get a chance to upload the Kinesis system consumer patches? Thanks a lot! -Yi On Thu, Oct 1, 2015 at 10:28 AM, Navina Ramesh wrote: > Thanks, Renato! :) > > On Thu, Oct 1, 2015 at 10:25 AM, Renato Marroquín Mogrovejo < > renatoj.marroq...@gmail.com> wrote: > > > Hi Navina,

Re: Review Request 44820: SAMZA-896 : Improvements to thread-safety in ContainerRequestState

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44820/#review123795 --- Fix it, then Ship it! lgtm. Fix it and then Ship it! samza-ya

Re: Review Request 44772: SAMZA-893 Fix the host affinity expiration logic bug introduced in SAMZA-867 and fix the tests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44772/#review123780 --- Can you also pull in your fix in SAMZA-897? I can't run ./check-al

Re: Review Request 44772: SAMZA-893 Fix the host affinity expiration logic bug introduced in SAMZA-867 and fix the tests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44772/#review123776 --- samza-yarn/src/main/java/org/apache/samza/job/yarn/HostAwareConta

Re: Review Request 44866: SAMZA-897 fix the backward-incompatible use of getOrDefault

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44866/#review123760 --- Ship it! lgtm! - Jagadish Venkatraman On March 15, 2016, 9:2

Re: Review Request 44866: SAMZA-897 fix the backward-incompatible use of getOrDefault

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44866/#review123754 --- Ship it! Thanks for fixing this. Tip: You should always run ./c

Review Request 44866: SAMZA-897 fix the backward-incompatible use of getOrDefault

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44866/ --- Review request for samza, Navina Ramesh, Jagadish Venkatraman, and Yi Pan (Data

Re: Review Request 44775: SAMZA-894 : Refactor logic that handles allocated containers

> On March 14, 2016, 6:51 a.m., Navina Ramesh wrote: > > samza-yarn/src/main/java/org/apache/samza/job/yarn/ContainerRequestState.java, > > line 149 > > > > > > I remember specifically not simplifying the conditions

Re: Review Request 44775: SAMZA-894 : Refactor logic that handles allocated containers

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44775/#review123745 --- Ship it! Ship It! - Navina Ramesh On March 14, 2016, 6:02 a.

Re: Running hello-samza for the first time

Hey Maurice, You're right about getOrDefault and it looks like it was my mistake. I'll file a JIRA and patch shortly. Apologies for the trouble. -Jake On Tue, Mar 15, 2016 at 1:08 PM, Maurice McCabe wrote: > Hi Jagadish, > > As I recall compiling samza (with JDK7) during > bin/grid bootstrap >

Re: Running hello-samza for the first time

Hi Jagadish, As I recall compiling samza (with JDK7) during bin/grid bootstrap resulted in compiler error on https://github.com/apache/samza/blob/bfba03b7bea731ffe7db1ed7e2a6441369e2cd9a/samza-core/src/main/scala/org/apache/samza/config/TaskConfig.scala#L97 getOrDefault() is a java 8 feature (AFA

Re: Review Request 44405: SAMZA-882 - Detect partition count changes in input streams

> On March 14, 2016, 11:46 p.m., Yi Pan (Data Infrastructure) wrote: > > samza-core/src/main/scala/org/apache/samza/coordinator/StreamPartitionCountMonitor.scala, > > line 78 > > > > > > Won't this be redundant w/ th

Re: Review Request 44604: split deployment logic

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44604/ --- (Updated March 15, 2016, 5:33 p.m.) Review request for samza and Yi Pan (Data I