Re: MM2 for DR

Hi Ryanne, Please could you elaborate a bit more about the active-active recommendation? Thanks in advance On Mon, Feb 10, 2020 at 10:21 PM benitocm wrote: > Thanks very much for the response. > > Please could you elaborate a bit more about "I'd > arc in that direction. Instead of migrating

Re: [HELP]

francis lee francislee...@outlook.com > 在 2020年2月11日，20:12，Bruno Cadonna 写道： > > Hi Francis, > > You need to sign-up to the Apache wiki at > https://cwiki.apache.org/confluence/signup.action > > Best, > Bruno > > On Tue, Feb 11, 2020 at 1:05 PM 萨尔卡

Re: [HELP]

Hi Francis, You need to sign-up to the Apache wiki at https://cwiki.apache.org/confluence/signup.action Best, Bruno On Tue, Feb 11, 2020 at 1:05 PM 萨尔卡 <1026203...@qq.com> wrote: > > i don't have a apache id. how can i apply one for create KIP? > > > > Have a nice dayFrancis Lee > > > QQ :

?????? [HELP]

i don't have a apache id. how can i apply one for create KIP? Have a nice dayFrancis Lee QQ : 1026203200

RE: Mirror Maker: supplying broker properties with SSL password encrypted

Anyone has any suggestions?? From: Chandrajeet Padhy Sent: Monday, February 10, 2020 12:01 PM To: users@kafka.apache.org Subject: Mirror Maker: supplying broker properties with SSL password encrypted Is there a way to supply the consumer.config/producer.config property files having encrypted

Re: "Skipping record for expired segment" in InMemoryWindowStore

Hi Jiří, Hmm, that is a mystery indeed. to inspect the log, you could try kafka-dump-log (I've never used it). What I have done before is use kafka-console-consumer, with the following option specified: --property properties include:

Re: "Skipping record for expired segment" in InMemoryWindowStore

Hi Bruno, John and Sophie, thank you very much for quick responses, you are the best. After thinking about it a little bit more, it seems fishy. >From logs, I see that it is not happening when application is running normally. I have checked timestamps (windowStartTimestamp) - connecting local

Re: "Skipping record for expired segment" in InMemoryWindowStore

Is it possible that during normal processing these records were actually dropped (eg due to a deserialization exception)? During restoration we actually just copy plain bytes from the changelog directly, so if this was an optimized source table it's possible that records which were supposed to be