Upgrade Failing Due to FlinkTaskManager Java Services Not Running
search cancel

Upgrade Failing Due to FlinkTaskManager Java Services Not Running

book

Article ID: 437537

calendar_today

Updated On:

Products

VCF Operations for Networks VMware vSphere ESXi

Issue/Introduction

This article addresses an upgrade failure in VCF Operations for Networks (formerly Aria Operations for Networks/vRNI) where the FlinkTaskManager Java services fail to start or stay running during the upgrade process.

Symptoms: The upgrade process stalls or rolls back. Inspection of services reveals that flink-taskmanager is not in a running state, preventing the cluster from reaching a healthy status for the update.

Environment

VCF Operations for Networks 9.x

Configurations: Distributed deployments or environments with strict network security policies/firewalls.

Cause

The failure is caused by a connectivity blockage. The upgrade requires specific communication ports to be open for Flink services to coordinate tasks. If these ports are not reachable or if the virtual machines are subject to restrictive security policies (such as NSX Distributed Firewall rules without proper exclusions), the FlinkTaskManager service will fail to initialize.

This is caused due customer have not enabled the Ports, 8030 ,8088 , 8025 , 45454(No details in the Doc).

Resolution

Firewall ports should be enabled as per  Ports.broadcom.com for connectivity

Follow these steps to resolve the connectivity issues and allow the upgrade to proceed:

  • Verify Service Status: Log in to the CLI of the affected node(s) and check the status of the Flink services:
    bash

    service flink-taskmanager status
  • Update Firewall Exclusion Lists: Ensure that the VCF Operations for Networks VMs are added to the Exclusion List of any local or distributed firewalls (e.g., NSX DFW) to prevent inter-node communication drops during the upgrade.
  • Validate Port Connectivity: Ensure all required ports are open. Refer to the official Broadcom port requirements:
  • Navigate to ports.broadcom.com and search for VCF Operations for Networks.
  • Verify that internal cluster communication ports (specifically those used by Apache Flink) are not blocked by intermediate physical or virtual firewalls.
  • Restart Services: Once connectivity is restored, restart the Flink services:
    bash

    service flink-taskmanager restart
  • Resume Upgrade: Retry the upgrade process through the administrative console.

Additional Information

Ports.broadcom.com/home/VMware-Aria-Operations-for-Networks

Documentation Deficiency identified regarding specific port updates for version 9.0.x.