-
Notifications
You must be signed in to change notification settings - Fork 219
Cannot get secondary resource from context after operator restart #1299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
thx @morhidi, will take a look. This on first guess could be related to the ordering of event sources and/or their indexes, will dig deeper, and try to come up with a solution. |
The problem is when there is "many-to-one" or "many-to-many" relationship between the primary and the secondary resources. This replicates the case for Flink Operator. In this example the primary resource referencing the secondary in the spec (by name) - there is no owner reference or annotation on the secondary resource. Without a Unfortunately there is no efficient way to cover this, other way then having |
Will create a separate issue to generalize the concept for event sources for external resources for v3.1 |
Uh oh!
There was an error while loading. Please reload this page.
Hi folks,
users encountered a blocking issue FLINK-28008 in Flink Kubernetes Operator related to primary/secondary resources after upgrading it to JOSDK v3.0.2.
We are managing session jobs(primary resource) and session clusters(secondary resource) with the Operator. Once a session job finishes users usually delete it. However, when the Operator is restarted, newly submitted session jobs won't find the session cluster anymore. The session cluster must be deleted and recreated to make it work which is not an acceptable workaround in our case unfortunately. I've uploaded the repro logs here
Could you please take a look into this issue?
Thanks,
Matyas
The text was updated successfully, but these errors were encountered: