Hi all,
A requirement has been raised by a colleague and I wanted to see if there
is any interest in the community in adding the functionality to Apache
Kafka.
ConsumerGroupCommand tool in describe ('--describe' or '--describe
--offsets') mode currently lists all topics the group has consumed
Messages don't contain any information to what transaction they belong.
Note, that `transaction markers`, as special messages that only indicate
a commit or abort. There is no `transaction marker` _in_ a message.
-Matthias
On 8/2/18 12:04 PM, ma...@kafkatool.com wrote:
>
>
> This would
This would be useful, for example, showing messages belonging to the
same transaction.
thanks
marko
- Original Message -
From: users@kafka.apache.org
To:
Cc:
Sent:Tue, 31 Jul 2018 14:40:20 -0700
Subject:Re: Viewing transactional markers in client
No. Transacti
Hi Matthias,
Thanks for the response.
I found the issue, actually my streaming job was still writing to the topic
even after I deleted it.
And my brokerhad default setting of auto.create.topic. So the topic was
created again.
Thanks
Pulkit
On Wed, Aug 1, 2018 at 12:57 PM, Matthias J. Sax
wrote:
Hi Guys,
I found lots of warning log in broker's server.log, any idea you have ? my
major concern why `failed due to null` will happen ? can I see it zookeeper
not available at that moment ?
WARNING log :
[2018-07-20 20:47:34,868] WARN Conditional update of path
/brokers/topics/HeartBeat/parti
Interested, will put some time learn about opentracing.org.
On Thu, Jul 19, 2018 at 9:34 AM, Christopher Smith
wrote:
> This sounds like a pretty good use case for opentracing.org. There is some
> nice integration with Kafka now too.
>
> --Chris
>
> On Thu, Jul 19, 2018, 8:26 AM Dan Rosanova
>
Hello,
I'm unable to start the zookeeper as well as Kafka. I tried by downloading the
zookeeper separately & now I'm able to start the zookeeper.
Coming to Kafka-server, It throws an error message "wmic is not recognized as
an internal or external command", I resolved it by adding the
"C:\Windo
Hi,
I'd like to restore a configuration for a topic which was previously
overriden with the AdminClient provided in the kafka-client library.
For example if I create a topic "test-topic" with the configuration "
delete.retention.ms=8641", I'd like to be able to reset this
configuration to def
Related issue:
https://lists.apache.org/thread.html/55df8a7310669a568c3b1e575e9f034ecc7cb242132c17e6df533134@%3Cusers.kafka.apache.org%3E
On Thu, Aug 2, 2018 at 4:29 PM Darpan Patel wrote:
> Hi guys,
>
> Recently I upgraded from Kafka 0.10 version to kafka 1.0 on one of the
> clusters.
> After t
Hi guys,
Recently I upgraded from Kafka 0.10 version to kafka 1.0 on one of the
clusters.
After the upgrade, we notice that for most of the topics's partitions ( if
topic has 8 partitions, at least for 5 partitions) we have Leader : -1 and
ISR : blank.
For example here is the example of describe
10 matches
Mail list logo