[lustre-discuss] lustre-discuss Digest, Vol 180, Issue 23

[Sid Young]

>
> LNET on the failover node will be operational as its a separate service,
> you can check it as shown below and do a "lnetctl net show":
>

[root at hpc-mds-02 ~]# systemctl status lnet
● lnet.service - lnet management
   Loaded: loaded (/usr/lib/systemd/system/lnet.service; disabled; vendor
preset: disabled)
   Active: active (exited) since Mon 2021-03-08 15:19:07 AEST; 2 weeks 1
days ago
  Process: 25742 ExecStart=/usr/sbin/lnetctl import /etc/lnet.conf
(code=exited, status=0/SUCCESS)
  Process: 25738 ExecStart=/usr/sbin/lnetctl lnet configure (code=exited,
status=0/SUCCESS)
  Process: 25736 ExecStart=/sbin/modprobe lnet (code=exited,
status=0/SUCCESS)
 Main PID: 25742 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/lnet.service

Mar 08 15:19:07 hpc-mds-02 systemd[1]: Starting lnet management...
Mar 08 15:19:07 hpc-mds-02 systemd[1]: Started lnet management.
[root at hpc-mds-02 ~]#

Its only the disk management that is down on the failover node.....

Sid

>
>
>     Imho, LNET to a failover node _must_ fail, because LNET should not be
> up on the failover node, right?
>
>     If I started LNET there, and some client does not get an answer
> quickly enough from the acting MDS, it
>     would try the failover, LNET yes but Lustre no - that doesn't sound
> right.
>
>
>     Regards,
>     Thomas
>
>     --
>     --------------------------------------------------------------------
>     Thomas Roth
>     Department: Informationstechnologie
>     Location: SB3 2.291
>     Phone: +49-6159-71 1453  Fax: +49-6159-71 2986
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20210324/b01c5af9/attachment.html>