> On Jan 27, 2016, at 8:25 PM, Sivananda Reddys Thummala Abbigari
> wrote:
>
> Hi,
>
> # *Kafka Version*: 0.8.2.1
>
> # *My consumer.propeties have the following properties*:
>exclude.internal.topics=false
>offsets.storage=kafka
>dual.commit.enabled=false
>
> # With the above configu
Storing offsets in Kafka frees up zookeeper writes for offset sync.so I
think it's preferred one to use whenever possible
On Thursday, October 29, 2015, Mayuresh Gharat
wrote:
> You can use either of them.
> The new kafka consumer (still under development) does not store offsets in
> zookeeper.
You can use either of them.
The new kafka consumer (still under development) does not store offsets in
zookeeper. It stores in kafka.
Thanks,
Mayuresh
On Wed, Oct 28, 2015 at 7:26 AM, Burtsev, Kirill <
kirill.burt...@cmegroup.com> wrote:
> Which one is considered preferred offset storage: zooke
So, when using the high level consumer, only offset.storage needs to be
set, and the High level API will take care of committing the offsets
automatically every so often.
If using the simple consumer API, call commitOffsets and set versionId on
the OffsetCommitRequest¹s constructor to be 1 to comm
>If you want to "move" offsets from zookeeper to Kafka then yes you
>need to have a phase where all consumers in your group set dual commit
>to true. If you are starting a fresh consumer group then you can
>turn off dual-commit.
I followed these steps to move the offsets from zookeeper to kafka:
1.
> Is it mandatory to use the zookeeper that comes with kafka for offset
> storage to be migrated to kafka?
If you want to "move" offsets from zookeeper to Kafka then yes you
need to have a phase where all consumers in your group set dual commit
to true. If you are starting a fresh consumer group th
