oint, FlinkKafkaConsumer would log the starting offset of
> Kafka partitions.
>
> WRT `auto.offset.rest` in Kafka configuration, it’s of a relatively low
> priority, and would only be used when there’s no restored state plus
> FlinkKafkaConsumer is set to `startFromGroupOffset`.
Howdy,
We're in the process of upgrading to 1.8. When restoring state to the new
cluster (using a savepoint) we are seeing our Kafka consumers restart from
the earliest offset. We're not receiving any other indication that our
state was not accepted as part of the deploy, e.g. we are not allowing
t this JIRA ticket [1] and check if it is related to
> the problems your are facing?
> If so, would you mind leaving a comment there?
>
> Thank you,
> Fabian
>
> [1] https://issues.apache.org/jira/browse/FLINK-8946
>
> 2018-05-31 4:41 GMT+02:00 Nikolas Davis :
>
>&g
s
> generated for them. The task id dimension will change on restart. If you
> name your metric based on this 'task_id' there would be a discontinuity
> with the old metric.
>
> On Wed, May 30, 2018 at 4:49 PM, Nikolas Davis
> wrote:
>
>> Howdy,
>>
>>
Howdy,
We are seeing our task manager JVM metrics disappear over time. This last
time we correlated it to our job crashing and restarting. I wasn't able to
grab the failing exception to share. Any thoughts?
We track metrics through the MetricReporter interface. As far as I can tell
this more or l
