Re: Executing Samza jobs natively in Kubernetes

2015-12-14 Thread Jagadish Venkatraman
Hi Elias, Thank you so much for your explanation. I'm looking into improving Samza Standalone and your design-inputs were very useful. Cheers, Jagadish On Mon, Dec 14, 2015 at 12:47 PM, Elias Levy wrote: > On Mon, Dec 14, 2015 at 11:55 AM, Jagadish Venkatraman < > jagadish1...@gmail.com> wrote

Review Request 41365: SAMZA-838: negative rocksdb.ttl.ms is not handled correctly

2015-12-14 Thread Tao Feng
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/41365/ --- Review request for samza. Repository: samza Description --- rocskdb ttl

Re: Executing Samza jobs natively in Kubernetes

2015-12-14 Thread Elias Levy
On Mon, Dec 14, 2015 at 11:55 AM, Jagadish Venkatraman < jagadish1...@gmail.com> wrote: > > Thanks for the great work! This is super-helpful. Another cool feature is > that this implementation pushes alot of failure handling/restarting to the > cluster manager. > > I've some questions on the imple

Re: Executing Samza jobs natively in Kubernetes

2015-12-14 Thread Jagadish Venkatraman
Hey Elias, Thanks for the great work! This is super-helpful. Another cool feature is that this implementation pushes alot of failure handling/restarting to the cluster manager. I've some questions on the implementation. 1. It's my understanding that each container is a separate pod. When a pod c

Re: Random connection errors

2015-12-14 Thread Yi Pan
Hi, Kishore, First, I would like to ask which version of Samza you are running? And if you can attach the log and config of your container (i.e. I assume the log you attached here is a container log?), it would be greatly helpful. Thanks a lot! -Yi On Mon, Dec 14, 2015 at 5:07 AM, Kishore N C

Random connection errors

2015-12-14 Thread Kishore N C
Hi, I have a 25 node Samza cluster and I am running a job on a dataset of a billion records that is backed by a 7 node Kafka cluster. Some of the tasks on some of the Samza nodes don't seem to start at all (while other tasks run fine on other nodes). The specific error message I see is in the tas