Wrong/missing link speed detection leads to bad recovery limit setting and bad recovery performance
Details
| Detail name | Value |
|---|---|
| Changelog Number | 26101 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0 |
| Fix Versions | Exasol 2026.1.0 |
| Resolution Date | 2026-05-15 |
Description
In some client environments, the network interface controller (NIC) speed was not detected properly, resulting in the speed being set to default and unexpectedly long duration for recovery operations (like storage segment move).
Workaround
Contact Exasol Support to guide you through setting the connection speed manually.
Fix
The issue was resolved by implementing a new API for ethtool (the old one is kept as a fallback) and supporting a wider and more flexible range of NIC speed negotiation.
