-
Notifications
You must be signed in to change notification settings - Fork 468
[FLINK-28574] Bump the JOSDK version to 3.2.1 #362
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
Conversation
Thanks @SteNicholas, it seems that bumping the fabric8 client has further implications - please double check the test failures:
|
Thanks @SteNicholas for the contrib! Few thoughts on this change:
|
I follow the bump step of JOSDK and bump the fabric8 client to 6.1.1.
Holding this PR at least till we release 1.2 makes sense to me. |
Hi @SteNicholas It'd be great if you could try to fix the CI errors, i.e. Thanks, |
b09f25c
to
ba1a374
Compare
ba1a374
to
3ce3009
Compare
@morhidi @mbalassi , the Java Operator SDK releases the 3.2.1 and 4.0.0 version, in which the Fabric Client version is 5.12.3 in v3.2.1 and the version is 6.1.1 in v4.0.0. I have bumped the version of Java Operator SDK to v3.2.1 that separates executor service for workflow. PTAL. BTW, Fabric8 Kubernetes Client 6.1.1 is most likely a breaking change, hence we could bump the version to 4.0.0 in Flink K8S operator 1.3 version. WDYT? |
@@ -113,6 +113,9 @@ private void overrideOperatorConfigs(ConfigurationServiceOverrider overrider) { | |||
} else { | |||
LOG.info("Configuring operator with {} reconciliation threads.", parallelism); | |||
overrider.withConcurrentReconciliationThreads(parallelism); | |||
// feat: separate executor service for workflow | |||
// https://github.com/java-operator-sdk/java-operator-sdk/pull/1371 | |||
overrider.withExecutorService(Executors.newFixedThreadPool(parallelism)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @SteNicholas Could you please explain why we need this extra config here? Is it ok if we control it with the same config?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @csviri
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
normally only overrider.withConcurrentReconciliationThreads(parallelism);
if you don't want to replace the executor service with a different flavor (thus other than a fixed thread pool).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@csviri @morhidi, this change comes from FlinkOperatorTest.java#L54, which get the ExecutorService
with default thread number 10 and the concurrentReconciliationThreads()
returns the default thread number.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Talked to @csviri offline, he'll clarify this part in a bit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, sorry, this seems to be an issue with the overrider, created a PR to fix it
operator-framework/java-operator-sdk#1484
pls for now override the service creation like above: overrider.withExecutorService
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SteNicholas yes, will backport it to 3.x
Hi @SteNicholas, if we stick with the current fabric8 version I don't see any problems merging this PR with the upcoming FOv1.2 release. |
+1 LGTM |
What is the purpose of the change
Java Operator SDK has released 3.2.1 version. Bump the JOSDK version to 3.2.1.
Brief change log
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Does this pull request potentially affect one of the following parts:
CustomResourceDescriptors
: (yes / no)Documentation