Re: Re: failed when job graph change

2024-01-24 Thread nick toker
Hi i adding a new sink that was not exists in the graph 1. stop with save point 2. run the the new graph with the new sink operator ( from save point) in this case the job stuck in initializing forever because cant complete transaction ( on the new operator , kafka topic) i dont understand how

Re: Re: failed when job graph change

2024-01-24 Thread Feng Jin
Hi nick If you want to modify the sink operator , I think you can modify the uid of the operator to avoid restoring the state that does not belong to it. Best, Feng On Thu, Jan 25, 2024 at 1:19 AM nick toker wrote: > hi > > i didn't found anything in the log > but i found that it happened

Re: Re: failed when job graph change

2024-01-24 Thread nick toker
hi i didn't found anything in the log but i found that it happened when i add a new sink operator and because i work with checkpoints the flink can't finish the transaction ( the new topic in kafka not part of the transaction before i added the new sink operator) so i must cancel the job to

Re: failed when job graph change

2023-12-03 Thread nick toker
Hi restart the job it's ok and i do that , but i must cancel the job and submit a new one and i dont want the data from the state forget to mention that i use the parameter "-allowNonRestoredState" my steps: 1. stop the job with savepoint 2. run the updated job ( update job graph) from