Hi Team,
I can't find any documentation or guidance on the expectation of the
downgrade of stateful Kafka stream application (which has different rocksdb
versions embedded).
For example, if we upgrade from 2.2 to 2.5 (with binary upgrade only
and using the same eager protocol) and somehow f
Did you ever restart your brokers to pick up the config changes?
On Wed, Dec 16, 2020 at 9:52 AM 路人 wrote:
> Dear Sir/Madam
> I am using kafka,but one problem in here. I changed
> "auto.create.topics.enable=false", but kafka producer can build topic. I
> would to konw the true methods to pr
Hi Anthony,
Great thanks for the update, glad to be present within the community!
We'll also update our tech blog to this link,
Thanks for your help, and stay well,
Antoine
From: Anthony Middleton
Sent: 16 December 2020 22:14
To: CRASKE Antoine
Cc: users@kafka.apache.org; Ale Murray
Subject
Hi,
I have a question regarding how to migrate a consumer when the
subscribing topic has been migrated to the target Kafka broker.
Suppose a consumer is consuming from topic1 at the source Kafka
broker. When MM2 mirrors this topic using options
source.cluster.alias="", replication.policy.separator=
+1 (non-binding) ... I used the binaries (Scala 2.12) and the staged Maven
artifacts - all seems to work fine. Thanks.
Jakub
On Wed, Dec 16, 2020 at 3:53 PM Bill Bejeck wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the seventh candidate for release of Apache Kafka 2.
Hey Ming,
There should not be any issues in downgrading from 2.5 to 2.2, and if
you stayed on the eager protocol then you can do the downgrade in a
single rolling bounce.
It sounds like your main concern here is with the RocksDB version bump,
and whether there would be any problems reading/openin
I'm answering to my own mail and would like to hear if this assumption
is correct.
it looks like I need 2.7.0 to have the automatic translation.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-545%3A+support+automated+consumer+offset+sync+across+clusters+in+MM+2.0
for earlier versions, there
Thanks for driving this release! I built from the tag and ran the tests,
and verified the signatures.
+1 (binding)
Sophie
On Thu, Dec 17, 2020 at 3:53 PM Jakub Scholz wrote:
> +1 (non-binding) ... I used the binaries (Scala 2.12) and the staged Maven
> artifacts - all seems to work fine. Thank
Navneeth,
You may need this JVM option:
-XX:-OmitStackTraceInFastThrow
as some stack frame information can be optimized away by default by some
JVMs leaving us blind to the real issue.
HTH
On Wed, Dec 16, 2020 at 4:15 AM John Roesler wrote:
> Hi Navneeth,
>
> I'm sorry for the trouble.
>
>
+1 (binding)
Thank you for the release, Bill!
I validated signatures, built from source package and ran the perf
producer/consumer to validate.
On Wed, Dec 16, 2020 at 6:53 AM Bill Bejeck wrote:
>
> Hello Kafka users, developers and client-developers,
>
> This is the seventh candidate for releas
Looks like you have your votes Mickael. :)
Ismael
On Fri, Dec 11, 2020 at 7:23 AM Mickael Maison wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the fourth candidate for release of Apache Kafka 2.6.1.
>
> Since RC2, the following JIRAs have been fixed: KAFKA-10811, KAF
Hi,
I was wondering if Apache Kafka is Fips Compliant or not. I see that
Confluent Kafka is FIPS
Complaint(https://docs.confluent.io/platform/current/security/compliance.html).
What about Apache Kafka, is there any documentation like above for
apache kafka also?
Regards,
Brajesh
12 matches
Mail list logo