Hi, I have the following three question regarding Apache Kafka streams.
1. I am in a position to use v 0.10.0.1 of Apache Kafka though so many bugs related to streams are fixed in the later versions. My application consists of low level processors that run for more than an hour for larger files (video transcoding). So, we use a session timeout and request timeout of 2 hrs. streams.close() is stuck for a long time even the processors are idle. Is there a reason? Is there a work around for this version? 2. Also, what does processorContext.commit() do exactly? Does it save the position of application in a topology or commit consumed message offset in the partition? Though commits are handled automatically by streams, should context.commit() be called at the end of each processor in a topology? 3. In a topology, if two processor completes successfully and the application goes down during third processor execution, does it start from first when the application comes back? -- With Regards, Bala Prassanna I, 8124831208
