Gentle reminder.
+ users.
On Mon, Mar 16, 2020 at 11:27 PM mandeep gandhi
wrote:
> Hi,
>
> (PS - I did not use users list as this concerns some internals)
>
> I was trying to deploy the following config on a K8s cluster -
>
> Namespace - X1 Connect group id - G1Bootstrap servers - B1, B2
Ah, I'm sorry, this is not the setting you need (it's actually the period
before "Found ... topic-partitions").
Please, ignore my message :)
Ivan
On Tue, 17 Mar 2020 at 18:04, Ivan Yurchenko
wrote:
> Hi,
>
> You need to set refresh.topics.interval.seconds, which is 10 minutes by
> default.
>
>
Hi,
You need to set refresh.topics.interval.seconds, which is 10 minutes by
default.
Ivan
On Tue, 17 Mar 2020 at 17:45, Péter Sinóros-Szabó
wrote:
> Hey,
>
> Running a MM2 cluster to mirror from A->B clusters I noticed that when I
> add a new topic to A cluster, MM2 will notice it:
> [2020-03
Hey,
Running a MM2 cluster to mirror from A->B clusters I noticed that when I
add a new topic to A cluster, MM2 will notice it:
[2020-03-17 13:14:05,477] INFO Found 2719 topic-partitions on main. 1 are
new. 0 were removed. Previously had 2718.
(org.apache.kafka.connect.mirror.MirrorSourceConnector
Hello Kafka users, developers and client-developers,
This is the third candidate for release of Apache Kafka 2.5.0.
* TLS 1.3 support (1.2 is now the default)
* Co-groups for Kafka Streams
* Incremental rebalance for Kafka Consumer
* New metrics for better operational insight
* Upgrade Zookeeper
Hey,
I used the default settings. I think, but I didn't check it, it means it
flushed to disk in every 5 seconds.
I just switched to SSDs (it is kinda amazing to do this online on an AWS
EBS disk :D ) and it works fine now.
Regards,
Peter
On Sat, 14 Mar 2020 at 01:27, Eugen Dueck wrote:
> Hi P
Thanks, Israel. I agree with Gwen, this is a great list and would be useful
to add to our release candidate boilerplate. Since we found a blocker bug
on RC1, I'll go ahead and close voting. RC2 will be announced shortly.
-David
On Tue, Mar 17, 2020 at 10:46 AM Israel Ekpo wrote:
> Thanks for th
Sorry, this was meant to go to flink :)
On Mon, Mar 16, 2020 at 6:47 PM Vishal Santoshi
wrote:
> We have been on flink 1.8.x on production and were planning to go to flink
> 1.9 or above. We have always used hadoop uber jar from
> https://mvnrepository.com/artifact/org.apache.flink/flink-shaded-
Thanks for the feedback, Gwen. I will create JIRA tasks to track the items
shortly.
The JIRA tasks will document the goals, expectations and relevant Kafka
versions for each resource.
I will volunteer for some of them and update the JIRA tasks accordingly.
On Tue, Mar 17, 2020 at 12:51 AM Gwen
