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
ainer
> additions and removals. For e.g. if a new container is explicitly added or
> removed via a config change, the system would change the partition to
> container mapping (and persist it durably back in the coordinator stream).
>
> Thanks
> Kartik
>
>
>
> On Mon, Nov 30,
On Mon, Nov 30, 2015 at 12:31 PM, Jakob Homan wrote:
> This is awesome work.
Thanks. Feel like a hack, but it got the job done.
> Would be interested in opening JIRAs for the
> changes you need so we can start to process them?
>
I've opened:
- SAMZA-824
I've been exploring Samza for stream processing as well as Kubernetes as a
container orchestration system and I wanted to be able to use one with the
other. The prospect of having to execute YARN either along side or on top
of Kubernetes did not appeal to me, so I developed a KubernetesJob
I am exploring Samza for some of our use cases. As we have a lot of Ruby
developers, I decided to determine if we could use JRuby with Samza. After
some work, I've been able to write Ruby jobs. To demonstrate the details,
I've ported the Hello Samza project to JRuby. You can find the port at