Re: Review Request 36545: SAMZA-682 Refactor Coordinator stream messages

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36545/#review93826 --- Ship it! Thanks for testing with Zopkio ! - Navina Ramesh On Jul

Re: Review Request 36006: Writing a tool to read from the coordinator stream and react to config changes accordingly.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36006/#review93820 --- samza-core/src/main/scala/org/apache/samza/job/JobRunner.scala (lin

Re: Review Request 36471: Autoscaling for samza (work in progress)

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36471/#review93785 --- As discussed, we definitely need a document on the auto-scaling desi

Re: [DISCUSS] Release 0.10.0

Hi, Guozhang, Good call. I moved SAMZA-697 out of 0.10.0. Boris is still working on that and it is not clear yet whether this separation of class loaders will be ready in 0.10.0. Thanks! -Yi On Fri, Jul 31, 2015 at 10:12 AM, Guozhang Wang wrote: > Would SAMZA-697 worth adding to 0.10.0 as wel

Re: Review Request 35445: SAMZA-693: Very basic HDFS Producer service for Samza

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35445/ --- (Updated July 31, 2015, 8:40 p.m.) Review request for samza. Repository: samz

Re: Review Request 35445: SAMZA-693: Very basic HDFS Producer service for Samza

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35445/ --- (Updated July 31, 2015, 7:53 p.m.) Review request for samza. Repository: samz

Re: Review Request 35445: SAMZA-693: Very basic HDFS Producer service for Samza

> On July 30, 2015, 6:59 p.m., Yan Fang wrote: > > samza-hdfs/src/main/scala/org/apache/samza/system/hdfs/writer/JobNameDateTimeBucketer.scala, > > line 40 > > > > > > My overall concern here is that, if there are mo

Re: Coordinator URL always 127.0.0.1

I realize the JC runs in the AM YARN container. The SamzaContainers run in their own YARN containers, which may or may not be on the same node as the AM in the YARN grid. My point is simply that when they are not, it does not work. This is because the AM is telling the SamzaContainers to fet

Re: Coordinator URL always 127.0.0.1

Hi Tommy, I am not sure what you mean below: {quote} this context by container I meant the SamzaContainer. What we are seeing is that jobs only start when YARN happens to place the AM and SamzaContainer(s) on the same node.Which is increasingly unlikely as you increase container count for your job

Re: [DISCUSS] Release 0.10.0

Would SAMZA-697 worth adding to 0.10.0 as well? Guozhang On Thu, Jul 30, 2015 at 6:45 PM, Yan Fang wrote: > For SAMZA-747, may ping Naveen or Chris. :) > > They have the permission to publish to maven. From the discuss > , they seem ready for the

Re: Coordinator URL always 127.0.0.1

Hey Yan, -- I do not quite understand this part. AM essentially is running in a container as well. And the http server is brought up in the same container Sorry, the term "container" is overloaded. In this context by container I meant the SamzaContainer. What we are seeing is that jobs only s

Re: Review Request 36545: SAMZA-682 Refactor Coordinator stream messages

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36545/ --- (Updated July 31, 2015, 12:49 p.m.) Review request for samza. Changes ---

Review Request 36985: SAMZA-749 Improve documentation for integration tests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36985/ --- Review request for samza. Repository: samza Description --- The integrat

Re: Review Request 36545: SAMZA-682 Refactor Coordinator stream messages

> On July 24, 2015, 6:01 p.m., Navina Ramesh wrote: > > Thanks for picking this up! It feels good to look at a refactored code. > > > > One suggestion: Please run all the intergration test (including the zopkio > > tests) before checking in this patch. I don't think we cleanly start and > > s