Hi
I'm using kafka 1.1.0, and encounter some issues which repaired in higher
version, e.g. KAFKA-6982, KAFKA-7165
I'm a bit afraid upgrading to newer version of kafka would bring some other
issues or bugs, so is it possible to add the pull request of corresponding
issue to current 1.1.0 source
I've just noticed that the store topic created automatically by our streams
app have different cleanup.policy.
I think that's the main reason I'm seeing that big read/write IO, having a
compact policy instead of delete would make the topic much smaller.
I'll try that to also see the impact on our s
Hi John,
thanks a lot for the great explanation and the links.
After I've sent the question I've researched a bit more about EOS and I'm
currently testing that out.
I'll read those links and see what I come up with!
Thanks and have a great day!
--
Alessandro Tagliapietra
On Tue, Jul 9, 2019 at
Hi Alessandro,
Sorry if I'm missing some of the context, but could you just keep
retrying the API call inside a loop? This would block any other
processing by the same thread, but it would allow Streams to stay up
in the face of transient failures. Otherwise, I'm afraid that throwing
an exception
I have a stream that is configured for exactly-once processing. I set
the "auto.offset.reset" of this stream to "none" for two reasons:
1) If an exactly-once stream loses its offset for some reason, using
either of earliest or latest is dangerous: "earliest" implies
reprocessing data, and "latest"
Hi Bruno,
Oh I see, I'll try to add a persistent disk where the local stores are.
I've other questions then:
- why is it also writing that much?
- how do I specify the retention period of the data? Just by setting the
max retention time for the changelog topic?
- wouldn't be possible, for examp
Hello Colin,
I appreciate the time for reviewing this PR. I have now incorporated your
(and Matthias's) comments and the PR has been resubmitted. Please let me
know if there is more that we need to change.
Thanks again,
On Mon, 8 Jul 2019 at 23:50, Colin McCabe wrote:
> Hi M. Manna,
>
> I left
Hi Alessandro,
I am not sure I understand your issue completely. If you start your
streams app in a new container without any existing local state, then
it is expected that the changelog topics are read from the beginning
to restore the local state stores. Am I misunderstanding you?
Best,
Bruno
Now that makes sense :)
Thanks
On Tue, Jul 9, 2019 at 1:43 AM Sophie Blee-Goldman
wrote:
> Hi Nitay,
>
> InMemoryKeyValueStore is in the internal package, not part of the public
> API, so it is not meant to be used directly since it's implementation may
> change at any time (as has happened here
