Kafka Streams Transformer: context.forward() from different thread

2017-10-10 Thread Murad Mamedov
Hi, here is the question: Transformer's transform() implementation starts some processing asynchronously, i.e. transform() implementation returns null. Then once asynchronous processing is complete in another thread, is it correct to call context.forward() from that thread? Thanks in advance

Re: kafka in unrecoverable state

2017-08-25 Thread Murad Mamedov
, Dan Markhasin wrote: > If you run kafka-topics.sh --describe --topic __consumer_offsets, does it > show that all replicas are in sync? > > On 23 August 2017 at 23:11, Murad Mamedov wrote: > > > Hi David, > > > > Thanks for reply. However, I don't have problem w

Re: kafka in unrecoverable state

2017-08-23 Thread Murad Mamedov
fsets-17 is [1], below required minimum [2] > > Please refer to > https://stackoverflow.com/questions/37960767/how-to- > change-the-replicas-of-kafka-topic. > Hope it helps! > > > On Aug 23, 2017 5:17 AM, "Murad Mamedov" wrote: > > > Hi, > > > &

Re: kafka in unrecoverable state

2017-08-23 Thread Murad Mamedov
Hi, Did you manage to find the root cause of this issue? Same thing happened here. Thanks in advance On Tue, Jun 13, 2017 at 7:50 PM, Paul van der Linden wrote: > I managed to solve it by: > - stopping and deleting all data on kafka & zookeeper > - stopping all consumers and producers > - sta

Record timestamp

2017-05-04 Thread Murad Mamedov
Hi, In Producer record, we have timestamp. - Where it is actually stored, if stored? - When producing resorts with KStream.to() which timestamp is used, if used? In order to guarantee proper timestamp, do we have to always implement timestamp extractor? Thanks in advance.

Time synchronization between streams

2017-04-26 Thread Murad Mamedov
Hi, Suppose that we have two topics, one with each event size 100 bytes and the other each event size 5000 bytes. Producers are producing events (with timestamps) for 3 days in both topics, same amount of events, let assume 10 events in each topic. Kafka Client API consumers will obviously co