In NettyBootstrap we configure the low and high watermarks in the following order:
When the memory segment size is higher than the default high water mark, this throws an `IllegalArgumentException` when a client tries to connect. Hence, this unfortunately only happens during runtime when a intermediate result is requested. This doesn't fail the job, but logs a warning and ignores the failed configuration attempt, potentially resulting in degraded performance because of a lower than expected watermark.
A simple fix is to first configure the high water mark and only then configure the low watermark.