2020-08-22 11:48:09 UTC - Ali Ahmed: @Frank Kelly pulsar is backwards compatible with clients all the way back to 1.0 ---- 2020-08-22 12:15:22 UTC - N/A: @N/A has joined the channel ---- 2020-08-22 12:16:41 UTC - Aleksandr Razumov: @Aleksandr Razumov has joined the channel ---- 2020-08-22 16:49:06 UTC - Adriaan de Haan: @Sijie Guo It is very strange, the problem went away for a while and now it's back again. I didn't enable ackTimeout since duplicates would cause big problems for me. However, if duplicates could only occur in case of consumer crash it should be fine - however, I have a doubt in this regard ---- 2020-08-22 16:49:40 UTC - Adriaan de Haan: If I enable ackTimeout, will the message be re-delivered to the same consumer in a shared subscription? ---- 2020-08-22 16:50:46 UTC - Adriaan de Haan: Or is it possible that the redelivery can be done to a different consumer (that could be on a totally different machine) and that consumer would thus not have this ack in it's internal ack state? ---- 2020-08-22 16:59:08 UTC - Adriaan de Haan: I wonder if it might be related to something in the kubernetes routing ---- 2020-08-22 17:00:25 UTC - Adriaan de Haan: it can't be a network connectivity issue because the application is running on the same node as pulsar (at least on one of the 3 nodes, so I guess it is possible that it's networking related, but highly unlikely since they are all in the same datacenter and I don't see any other issues). ---- 2020-08-22 17:13:35 UTC - Adriaan de Haan: I'm still a bit of a newby to pulsar, but personally I gave up on functions altogether because I ran into a strange null-pointer exception issue that prevented me from getting functions working. I also found that the visibility into the function was limited (especially in the loading phase) so I ended up just writing consumers and producers that did the same. Running on the same kubernetes cluster as pulsar, I'm not sure what benefits functions bring to the table - specifically the function state would be useful if it would mean one could get away with not using another system/framework for storing state (I'm using apache ignite and mysql for my state requirements at the moment) ---- 2020-08-22 17:14:31 UTC - Adriaan de Haan: But the state API seemed to be a bit immature also, so when I ran into some stumbling blocks I went the other way. ---- 2020-08-22 17:17:50 UTC - Gilles Barbier: Thx for the feedback - for our part, we managed to have functions working, but have specific issues with states. As you mention, we want to use state specifically to avoid to bring another system to store states ---- 2020-08-22 17:19:02 UTC - Gilles Barbier: We are developing a workflow engine on top of Pulsar. Avoiding to add any additional required systems would be a huge bonus for us ----
