Re: Upgrade to 1.14.3

2022-01-28 Thread Robert Metzger
Hi Sweta,

yes, you can not run a Flink job compiled against Flink 1.13. against a
1.14 cluster. But if you are only using stable APIs of Flink, you should be
able to compile your job with the 1.14 dependencies without touching the
code.

See also:
https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/ops/upgrading/

> - How do I upgrade to 1.14.3 cluster without loosing running apps state?
I have even tried doing savepoint that did not revive the job.

Using a savepoint created with a job compiled against Flink 1.13, and
restoring it with a job compiled against 1.14 is the recommended approach.


On Tue, Jan 25, 2022 at 3:37 PM Sweta Kalakuntla 
wrote:

> Hi Ingo,
>
> So basically, I cannot deploy an older version of flink job in 1.14.3
> flink cluster, is it?
>
> Thanks,
> Sweta
>
> On Tue, Jan 25, 2022 at 4:02 AM Ingo Bürk  wrote:
>
>> Hi Sweta,
>>
>> there was a non-compatible change to SourceReaderContext#metricGroup in
>> the 1.14.x release line; I assume this is what you are seeing.
>>
>> Did you make sure to update the connector (and any other) dependencies
>> as well?
>>
>>
>> Best
>> Ingo
>>
>> On 25.01.22 05:36, Sweta Kalakuntla wrote:
>> > Hi,
>> >
>> > We are on flink 1.13.3 and trying to upgrade  the cluster to 1.14.3
>> > version. I see that job(on 1.13.3) is unable to start up because it
>> says
>> > it couldn't find metrics group(inside flinkkafkaconsumer class).
>> >
>> > - can I deploy 1.13.3 job on 1.14.3 cluster?
>> > - can I deploy 1.14.3 job on 1.13.3 cluster?
>> > - How do I upgrade to 1.14.3 cluster without loosing running apps
>> state?
>> > I have even tried doing savepoint that did not revive the job.
>> >
>> > Thank you,
>> > Sweta
>>
>


Re: Upgrade to 1.14.3

2022-01-25 Thread Sweta Kalakuntla
Hi Ingo,

So basically, I cannot deploy an older version of flink job in 1.14.3 flink
cluster, is it?

Thanks,
Sweta

On Tue, Jan 25, 2022 at 4:02 AM Ingo Bürk  wrote:

> Hi Sweta,
>
> there was a non-compatible change to SourceReaderContext#metricGroup in
> the 1.14.x release line; I assume this is what you are seeing.
>
> Did you make sure to update the connector (and any other) dependencies
> as well?
>
>
> Best
> Ingo
>
> On 25.01.22 05:36, Sweta Kalakuntla wrote:
> > Hi,
> >
> > We are on flink 1.13.3 and trying to upgrade  the cluster to 1.14.3
> > version. I see that job(on 1.13.3) is unable to start up because it says
> > it couldn't find metrics group(inside flinkkafkaconsumer class).
> >
> > - can I deploy 1.13.3 job on 1.14.3 cluster?
> > - can I deploy 1.14.3 job on 1.13.3 cluster?
> > - How do I upgrade to 1.14.3 cluster without loosing running apps state?
> > I have even tried doing savepoint that did not revive the job.
> >
> > Thank you,
> > Sweta
>


Re: Upgrade to 1.14.3

2022-01-25 Thread Ingo Bürk

Hi Sweta,

there was a non-compatible change to SourceReaderContext#metricGroup in 
the 1.14.x release line; I assume this is what you are seeing.


Did you make sure to update the connector (and any other) dependencies 
as well?



Best
Ingo

On 25.01.22 05:36, Sweta Kalakuntla wrote:

Hi,

We are on flink 1.13.3 and trying to upgrade  the cluster to 1.14.3 
version. I see that job(on 1.13.3) is unable to start up because it says 
it couldn't find metrics group(inside flinkkafkaconsumer class).


- can I deploy 1.13.3 job on 1.14.3 cluster?
- can I deploy 1.14.3 job on 1.13.3 cluster?
- How do I upgrade to 1.14.3 cluster without loosing running apps state? 
I have even tried doing savepoint that did not revive the job.


Thank you,
Sweta


Upgrade to 1.14.3

2022-01-24 Thread Sweta Kalakuntla
Hi,

We are on flink 1.13.3 and trying to upgrade  the cluster to 1.14.3
version. I see that job(on 1.13.3) is unable to start up because it says it
couldn't find metrics group(inside flinkkafkaconsumer class).

- can I deploy 1.13.3 job on 1.14.3 cluster?
- can I deploy 1.14.3 job on 1.13.3 cluster?
- How do I upgrade to 1.14.3 cluster without loosing running apps state? I
have even tried doing savepoint that did not revive the job.

Thank you,
Sweta