Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Adding missing logic to Kubernetes Scheduler to properly set the Remote Debug ports #3704

Merged
merged 1 commit into from
Aug 2, 2021

Conversation

nicknezis
Copy link
Contributor

The remote debug ports were being added to the Pod Spec, but the logic was never added to provide the port information to the Heron Executor which launches the Java processes.

Also there was an issue with the Kubernetes port name being larger than 15 characters. So I renamed it to fit the K8s spec.

@nicknezis nicknezis self-assigned this Jul 30, 2021
@nicknezis nicknezis changed the title Adding missing logic to provide Remote Debug ports to the Executor Adding missing logic to Kubernetes Scheduler to properly set the Remote Debug ports Jul 30, 2021
final Config configuration = getConfiguration();
final Config runtimeConfiguration = getRuntimeConfiguration();
if (TopologyUtils.getTopologyRemoteDebuggingEnabled(Runtime.topology(runtimeConfiguration))
&& numOfInstances != 0) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to get rid of this magic number here in the code? It's readable to me, but may not be to others.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I copied this code from another scheduler. If we change it, we should fix it everywhere. Any name suggestions? My gut feeling is that this one might be obvious, so ok to keep as is.

@nicknezis nicknezis merged commit d883db3 into master Aug 2, 2021
@nicknezis nicknezis deleted the nicknezis/k8s-remote-debug branch August 2, 2021 03:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants