Just for clarification - it will be completely impossible to login using openssh or some other priveledge separation protocol to the machine due
to the nature of unix sockets. So you will be unable to manage your
storage system just because it is in OOM - it is not what is expected
from reliable system.
The system is not OOM, it is in reclaim, a transient condition that will be
resolved in normal course by IO progress. However you raise an excellent
point: if there is any remote management that we absolutely require to be
available while remote IO is interrupted - manual failover for example -
then we must supply a means of carrying out such remote administration, that
is guaranteed not to deadlock on a normal mode memory request. This ends up
as a new network stack feature I think, and probably a theoretical one for
the time being since we don't actually know of any such mandatory login
that must be carried out while remote disk IO is suspended.
That is why you are not allowed to depend on main system's allocator
problems. That is why network can have it's own allocator.
But really, if you expect to run reliable block IO to Zanzibar over an sshJust pure openssh for control connection (admin should be able to
tunnel through a firewall, then you might also consider taking up bungie
jumping with the cord tied to your neck.
And the admin will be able to, but in the cluster stack itself we don't
bless such stupidity as emailing an admin to ask for a login in order to
break a tie over which node should take charge of DLM recovery.
No, you can't since openssh and any other priveledge separation
mechanisms use adtional sockets to transfer data between it's parts,
unix sockets require page sized allocation frequently which will endup
with 8k allocation in slab.
You will not be able to login using openssh.