FIX: DMVs fail when Big Data Cluster has multiple compute nodes in SQL Server 2019

Applies to: SQL Server 2019 on Linux


Assume that you deploy a BigData Cluster (BDC) with multiple compute nodes and call Dynamic Management Views (DMVs) associated with BDC or PolyBase. You may notice that most of the DMVS have missing or incomplete entries and cause errors to be logged by the Parallel Data Warehouse (PDW) Engine Service in the compute-0-0 pod.

For example, for all compute_nodes with a compute_node_id greater than 1, the following DMV query may have incomplete rows (with NULL values):
select compute_pool_id, compute_node_id, process_name, process_id from sys.dm_exec_compute_node_status
compute_pool_id      compute_node_id      process_name  process_id
0                               1                                  Engine             48
0                               1                                  DMS                44
1                               1                                  Engine             48
1                               1                                  DMS                44
1                               2                                  DMS                NULL

The following DMV query may return the wrongresult (missing rows for compute_node_id greater than 1):
select * from sys.dm_exec_dms_services

The following error can be foundin the PDW Engine Service logs in the compute-0-0 pod:
DateandTime [Thread:ThreadId] [GeneralInstrumentation:InternalPingErrorEvent] (Error, Low):
System.ServiceModel.Security.MessageSecurityException:Identity check failed for outgoing message. The expected DNS identity of theremote endpoint was 'compute-0-0.dkdomain.local' but the remote endpointprovided DNS claim 'compute-0-1.dkdomain.local'. If this is a legitimate remoteendpoint, you can fix the problem by explicitly specifying DNS identity'compute-0-1.dkdomain.local' as the Identity property of EndpointAddress whencreating channel proxy.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 


This issue is fixed in thefollowing cumulative update for SQL Server:
Aboutcumulative updates for SQL Server:
Each new cumulativeupdate for SQL Server contains all the hotfixes and all the security fixes thatwere included with the previous cumulative update. Check out the latestcumulative updates for SQL Server:


Learn about the terminology that Microsoft uses to describe software updates.