Why does TIBCO DataVirtualization try to use a different port than using the configured port?
Article ID: KB0076985
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | 7.0.x and higher |
Description
For the purpose of illustrating with an example, lets assume that TIBCO DataVirtualization (TDV) was configured to use base port 9500.
According to above configuration, firewall exceptions were made for ports 9500-9509. TDV may still be running, but the errors indicate that TDV is attempting to connect to port 9401.------------
QuorumCnxManager - Cannot open channel to -459655284 at election address redwood.internaldev.com/129.233.340.6:9401
java.net.NoRouteToHostException: No route to host (Host unreachable)
at java.net.PlainSocketImpl.socketConnect(Native Method)
------------
Opening ports 9400-9409 in firewall resolved the issue. Why did TDV attempt to access port 9401 instead of the configured port 9501?
Issue/Introduction
Resolution
The reason port 9401 is being accessed is that the Massively Parallel Processing (MPP) engine engine requires a port range of P-100 to P-100+6 (where P is the base port). For a base port of 9500, this range would be 9400 to 9406 as shown below.
Description How the port is calculated Example
Zookeeper Quorum Port P - 100 9500-100 = 9400
Zookeeper Election Port P - 100 + 1 9500-100 + 1 = 9401
Zookeeper Client Port P - 100 + 2 9500-100 + 2 = 9402
Drill HTTP Port P - 100 + 3 9500-100 + 3 = 9403
Drill User Port P - 100 + 4 9500-100 + 4 = 9404
Drill Server Bit Ports P - 100 + 5 and P - 100 + 6 9405 and 9406
Feedback
