UnsupportedOperationException: this should not happen: timestamp() is not supported in standby tasks.
Hi,
We have a Kafka streams application with "num.standby.replicas" = 1 and
with replication-factor of 2 for that topic. The application is crashing
with the following stack trace.
java.lang.UnsupportedOperationException: this should not happen:
timestamp() is not supported in standby tasks.\n\n\tat
org.apache.kafka.streams.processor.internals.ProcessorContextImpl.throwUnsupportedOperationExceptionIfStandby(ProcessorContextImpl.java:352)\n\n\tat
org.apache.kafka.streams.processor.internals.ProcessorContextImpl.timestamp(ProcessorContextImpl.java:328)\n\n\tat
org.apache.kafka.streams.state.internals.ChangeLoggingKeyValueBytesStore.log(ChangeLoggingKeyValueBytesStore.java:136)\n\n\tat
org.apache.kafka.streams.state.internals.ChangeLoggingKeyValueBytesStore.put(ChangeLoggingKeyValueBytesStore.java:78)\n\n\tat
org.apache.kafka.streams.state.internals.ChangeLoggingKeyValueBytesStore.put(ChangeLoggingKeyValueBytesStore.java:32)\n\n\tat
org.apache.kafka.streams.state.internals.MeteredKeyValueStore.lambda$put$4(MeteredKeyValueStore.java:197)\n\n\tat
org.apache.kafka.streams.processor.internals.metrics.StreamsMetricsImpl.maybeMeasureLatency(StreamsMetricsImpl.java:883)\n\n\tat
org.apache.kafka.streams.state.internals.MeteredKeyValueStore.put(MeteredKeyValueStore.java:197)\n\n\tat
Key Kafka streams application configuration details are as below:-
{replication.factor=1, num.standby.replicas=1, topology.optimization=all,
producer.partitioner.class=com.hpe.gravity.gravitycommon.utils.Murmur3Partitioner,
max.request.size=1048576, auto.offset.reset=earliest}
Is this a Kafka library issue or something wrong with the application
configuration?
thanks,
-sureshr
We have a Kafka streams application with "num.standby.replicas" = 1 and
with replication-factor of 2 for that topic. The application is crashing
with the following stack trace.
java.lang.UnsupportedOperationException: this should not happen:
timestamp() is not supported in standby tasks.\n\n\tat
org.apache.kafka.streams.processor.internals.ProcessorContextImpl.throwUnsupportedOperationExceptionIfStandby(ProcessorContextImpl.java:352)\n\n\tat
org.apache.kafka.streams.processor.internals.ProcessorContextImpl.timestamp(ProcessorContextImpl.java:328)\n\n\tat
org.apache.kafka.streams.state.internals.ChangeLoggingKeyValueBytesStore.log(ChangeLoggingKeyValueBytesStore.java:136)\n\n\tat
org.apache.kafka.streams.state.internals.ChangeLoggingKeyValueBytesStore.put(ChangeLoggingKeyValueBytesStore.java:78)\n\n\tat
org.apache.kafka.streams.state.internals.ChangeLoggingKeyValueBytesStore.put(ChangeLoggingKeyValueBytesStore.java:32)\n\n\tat
org.apache.kafka.streams.state.internals.MeteredKeyValueStore.lambda$put$4(MeteredKeyValueStore.java:197)\n\n\tat
org.apache.kafka.streams.processor.internals.metrics.StreamsMetricsImpl.maybeMeasureLatency(StreamsMetricsImpl.java:883)\n\n\tat
org.apache.kafka.streams.state.internals.MeteredKeyValueStore.put(MeteredKeyValueStore.java:197)\n\n\tat
Key Kafka streams application configuration details are as below:-
{replication.factor=1, num.standby.replicas=1, topology.optimization=all,
producer.partitioner.class=com.hpe.gravity.gravitycommon.utils.Murmur3Partitioner,
max.request.size=1048576, auto.offset.reset=earliest}
Is this a Kafka library issue or something wrong with the application
configuration?
thanks,
-sureshr
Comments
Post a Comment