I completely missed that in the docs (for me, j think it's because this is
the only operation I know of that requires that kind of confirmation).
Thanks!
-shargan
On Thu, Sep 21, 2017 at 12:41 Hans Jespersen wrote:
> Did you add the --execute flag?
>
> -hans
>
> > On Sep 21, 2017, at 11:37 AM,
Did you add the --execute flag?
-hans
> On Sep 21, 2017, at 11:37 AM, shargan wrote:
>
> Testing kafka-consumer-groups.sh in my dev environment, I'm unable to reset
> offsets even when CURRENT-OFFSET is inbounds. Again, it returns as if the
> change took effect but describe still shows the orig
Testing kafka-consumer-groups.sh in my dev environment, I'm unable to reset
offsets even when CURRENT-OFFSET is inbounds. Again, it returns as if the
change took effect but describe still shows the original value and client
behavior bears this out.
-shargan
On Wed, Sep 20, 2017 at 13:40 shargan
Hi there,
The Kafka servers in question were 0.11.0.0 this morning. I upgraded to
0.11.0.1 after discovering this issue but I don’t see any change. Scala
2.11.
A client using the new-style consumer groups is not consuming any new
messages because its current committed offset is out of range. I sh
Hi there,
The Kafka servers in question were 0.11.0.0 this morning. I upgraded to
0.11.0.1 after discovering this issue but I don’t see any change. Scala
2.11.
A client using the new-style consumer groups is not consuming any new
messages because its current committed offset is out of range. I sh
