Re: After upgrade to 2.13 2.8.1 getting message in log

in sync. I’m letting this run. Jim On 2/25/22, 7:09 PM, "Jim Langston" wrote: Hi all , after upgrading to 2.8.1 and restarting the brokers, one of the brokers is continually logging messages similar to this Feb 25 23:58:17 bigdata-worker2.dc.res0.

After upgrade to 2.13 2.8.1 getting message in log

Hi all , after upgrading to 2.8.1 and restarting the brokers, one of the brokers is continually logging messages similar to this Feb 25 23:58:17 bigdata-worker2.dc.res0.local WARN: (Logging.scala:70) [ReplicaFetcher replicaId=2, leaderId=0, fetcherId=0] Reset fetch offset for partition

Re: Upgrade choice between 0.11.0 and 1.0.1

After reading the blog from Neha https://www.confluent.io/blog/apache-kafka-goes-1-0/ I moved to the 1.0 platform in production .. Jim / On 3/27/18, 7:07 AM, "chou.fan" wrote: Hi, we are planning to upgrade our kafka cluster to benefit from the new

Re: Running kafka in containers

I think is an open-ended question we are all starting to ask as we are moving to K8 and docker environments. Do we stand up a Kafka cluster by itself, or do we pull Kafka in the K8 umbrella ? Jim On 3/22/18, 3:28 PM, "Jason Turim" wrote: What container orchestration

? compression

Hi all, Probably a common scenario: Kafka storage growing Added more disk space Calculation shows disk space growing fast Would like to compress topics Compression simple enough to implement Question: Would like to compress the current data, is there any sage advice ? It does not look simple,