Jon,
I looked through the code and found one possible explanation of your
observed exception:
1. Assume 2 running threads A and B, and one task t1 jut for simplicity.
2. First rebalance is triggered, task t1 is assigned to A (B has no
assigned task).
3. During the first rebalance callback, task t
java.lang.IllegalStateException: task [0_6] Log end offset of
RtDetailBreakoutProcessor-table_stream-changelog-6 should not change while
restoring: old end offset 26883455, current offset 2
6883467
at
org.apache.kafka.streams.processor.internals.ProcessorStateManager.restoreActiveState(Pr
ete stacktrace
>
> User provided listener
> org.apache.kafka.streams.processor.internals.StreamThread$1
> for group test failed on partition assignment
> java.lang.IllegalStateException: Log end offset should not change while
> restoring
> at org.apache.kafka.streams.processor.internals.
> Proce
listener
org.apache.kafka.streams.processor.internals.StreamThread$1
for group test failed on partition assignment
java.lang.IllegalStateException: Log end offset should not change while
restoring
at org.apache.kafka.streams.processor.internals.
ProcessorStateManager.restoreActiveState
StreamsConfig.CACHE_MAX_BYTES_BUFFERING_CONFIG
The only one cache parameter. Do you use code auto-completion? It's also
in the docs:
http://docs.confluent.io/current/streams/developer-guide.html#optional-configuration-parameters
-Matthias
On 12/12/16 8:22 PM, Jon Yeargers wrote:
> What is the
What is the specific cache config setting?
On Mon, Dec 12, 2016 at 1:49 PM, Matthias J. Sax
wrote:
> We discovered a few more bugs and a bug fix release 0.10.1.1 is planned
> already.
>
> The voting started for it, and it should get release the next weeks.
>
> If you issues is related to this ca
We discovered a few more bugs and a bug fix release 0.10.1.1 is planned
already.
The voting started for it, and it should get release the next weeks.
If you issues is related to this caching problem, disabling the cache
via StreamsConfig should fix the problem for now. Just set the cache
size to
Im seeing this error occur more frequently of late. I ran across this
thread:
https://groups.google.com/forum/#!topic/confluent-platform/AH5QClSNZBw
The implication from the thread is that a fix is available. Where can I get
it?
