GridServer 7.1.0 Hotfix10 has been released. Here are the release notes:
================================================================================
Introduction

Hotfixes are cumulative. 

================================================================================
Affected Components for 7.1.0_hotfix10

The following components are updated by this hotfix:
Engine Daemon

================================================================================
Closed Issues in 7.1.0_hotfix10 (This Release)

Engine Daemon
GS-20476
This release fixes a performance regression introduced in GridServer 7.1.0 Hotfix 09 (GS-19812).

Previously, the all-engine-info REST API queried the file server of every unique Engine host before returning a response. 
These queries were sequential and blocking, which increased the time-to-first-byte and could hold Broker HTTP threads. 
This resulted in delayed driver logins and asynchronous replies.

In HF-10, the appending-DDT lookup is separate from the EngineInfo APIs.
The hasAppendingDDT field is now removed from the EngineInfo responses of the all-engine-info, engine-info, 
engine-info-by-properties, and selected-engine-info REST APIs. These APIs no longer contact any Engine FileServer.

You can now retrieve the appending DDT status on demand through a new Admin API, EngineAdmin.hasAppendingDDT(long id). 
This functionality is also available through the the SOAP web service and the following endpoint:
GET /livecluster/rest/engine/ddt-status?id=<engine-id>
The system reports the status for each host rather than for each Engine instance. It does not require an instance parameter. 
All Engine instances under a single Engine ID share the same Daemon and FileServer. The API returns true if the host has 
untransferred DDT output, or immediately if any instance on the host is busy. Because the Broker queries the Engine FileServer, 
the call requires additional connection and query time. Any condition that leaves the status undetermined, such as an unknown 
Engine ID, a missing file server address, an unreachable host, a timeout exceeding three seconds, or an unreadable reply, 
results in an error. Older Engines (prior to 7.1.0 Hotfix 09) lacking a /ddt-status handler also report an error.

Alternatively, you can query the Engine file server directly using http://<host>:27159/ddt-status. If DDT TLS is enabled, 
use https://<host>:27159/ddt-status and provide a client certificate. This host-wide endpoint accepts no parameters and 
returns true or false. The Broker queries this endpoint internally.

================================================================================
To download this hotfix, login to the Support Portal and navigate to Downloads > Hotfixes > AvailableDownloads > DataSynapse > GridServer > 7.1.0.

GridServer 7.1.0 Hotfix10 Release Announcement