Hello Kafka developers and users,
As promised in the release plan
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554044,
we now have a release branch for 2.1.0 release. Trunk will soon be bumped
to 2.2.0-SNAPSHOT.
I'll be going over the JIRAs to move every non-blocker from thi
Deprecated scala consumers/producers are removed from 2.0 release. Old
consumer related options are removed from /kafka-consumer-groups.sh tool.
http://kafka.apache.org/documentation/#upgrade_200_notable
We missed updating some of the docs. Will be fixed in next release docs.
On Thu, Oct 4, 2018
Saw it, thank you.
Best regards
Patrik
> Am 04.10.2018 um 17:11 schrieb Matthias J. Sax :
>
> Thanks for the details.
>
> Seems like a fair assumption. I created a jira to track it:
> https://issues.apache.org/jira/browse/KAFKA-7480
>
> For now, there is not much you can do, because Streams har
Hi Kafka Users,
When does a "Summed recent Offsets" get reset in a topic ?
I have a Topic "test" on which this value didn't change over time even
after it passed the retention hours.
Also this topic has a stale consumer group "sub1" ..I'm unable to delete it.
*kafka-consumer-groups.sh --bootstra
Hi all,
I installed kafka_2.11-2.0.0 tarball on a CentOS server :
[kafka@oxelkk-bo-1:~] $ uname -a
Linux oxelkk-bo-1 3.10.0-862.11.6.el7.x86_64 #1 SMP Tue Aug 14 21:49:04 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
[kafka@oxelkk-bo-1:~] $
equipped with this JVM:
[kafka@oxelkk-bo-1:~] $ java -version
CONFIDENTIAL & RESTRICTED
Hi Everybody,
I'm facing a problem I don't manage to find an explanation.
I've got ian openshift pod with kafka 0.10.2.1 and a zookeeper 3.4.9. We have
only one topic feeded by a kafka connector running in another pod that sends
around 21 messages per second.
For some
Thanks for the details.
Seems like a fair assumption. I created a jira to track it:
https://issues.apache.org/jira/browse/KAFKA-7480
For now, there is not much you can do, because Streams hard codes to set
the policy to "none". Thus, a manual restart (that is gladly working as
you confirmed) it c
Hello Matthias
Thanks for looking into this.
A restart has worked, I can confirm that.
Before this problem happened we had some cluster issues which are still
being looked into, there were some leader changes and some offset commit
failures.
The consumer should not have lagged that much behind, but
