NFS nconnect support
-
Hi,
Any idea if NFS nconnect support is coming? This creates and allows for multiple tcp connections between hosts and storage. Truenas (CORE) 13 just got released, enabling this function :D. As far as I understand it, this will give us multiple tcp streams over an LACP link, truely aggregating traffic on multiple interfaces. (Until now, you needed to use iSCSI multipathing for this, which isnt able to thin provision.).
-
@reinvtv Linux kernel 5.3 or newer is needed for NFS nconnect. Current XCP 8.2 is only on 4.19..... so, no....
-
Only when we'll have a more recent kernel in Dom0
But this will come at some point. -
@olivierlambert said in NFS nconnect support:
Only when we'll have a more recent kernel in Dom0
But this will come at some point.Was just looking to ask the same about nconnect. Shame about the kernel support. Perhaps this is coming soon, as xcp-ng will have to change base distro? What's the progress on this?
-
There's no specific date. But we are working into that direction. First, replacing all Python 2 to 3, which is not a simple task, as you can imagine
-
@reinvtv said in NFS nconnect support:
As far as I understand it, this will give us multiple tcp streams over an LACP link, truely aggregating traffic on multiple interfaces. (Until now, you needed to use iSCSI multipathing for this, which isnt able to thin provision.).
You're neigher right nor wrong: LACP is more complex than just bundling NICs and in many cases it will NOT give you any benefit.
Why? Simple: For that you need to have NFS using multiple ports but stay with same MAC and IP, which means that your LACP balancing algo needs to be set (and support) L4.
Many just go L2 or L3 (means they decide on MAC or IP-Address).
As a quick search didn't answer me: If it even doesn't go that 'passive range' multiple port way: In typical environments it won't help you at all with LACP.One might correct my post.
Also interesting: https://vastdata.com/blog/meet-your-need-for-speed-with-nfs/
