Lustre discuss - Jun 2010 - Residual sessions on the luster cluster

Hey Guys,

Some of my users are reporting that sessions that they start on the lustre
cluster seem to live on if their session times out, or if they otherwise get
disconnected. This even happens when the session was in the foreground.
 Could the shared lustre fs be causing this?  Any ideas?

Thanks,
-J
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100618/82043e21/attachment.html

On Fri, 2010-06-18 at 10:55 -0700, Jagga Soorma wrote: 
> 
> Some of my users are reporting that sessions
What''s a "session" in the context of Lustre?  Lustre is a
filesystem and
there is no "user session" concept that I can think of.
> that they start on the lustre cluster seem to live on if their session
> times out, or if they otherwise get disconnected. This even happens
> when the session was in the foreground.  Could the shared lustre fs be
> causing this?
With the little bit of information you have provided, it does not seem
likely.  I think you need to debug this situation a bit more to decide
where the cause lies.

b.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100618/f7619ed9/attachment.bin

My apologies, should have been a bit more clear.  So the users home
directories reside on the lustre filesystem.  They login and start some
computational job in the foreground.  When their session times out or they
get disconnected their jobs are still running and need to be killed by
sending the kill signal.  The job should also die with the session if it is
running in the foreground.

-J

On Fri, Jun 18, 2010 at 10:55 AM, Jagga Soorma <jagga13 at gmail.com>
wrote:
> Hey Guys,
>
> Some of my users are reporting that sessions that they start on the lustre
> cluster seem to live on if their session times out, or if they otherwise
get
> disconnected. This even happens when the session was in the foreground.
>  Could the shared lustre fs be causing this?  Any ideas?
>
> Thanks,
> -J
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100618/c744fbcc/attachment.html

On Fri, 2010-06-18 at 11:04 -0700, Jagga Soorma wrote:
> My apologies, should have been a bit more clear.  So the users home
> directories reside on the lustre filesystem.  They login and start
> some computational job in the foreground.  When their session times
> out or they get disconnected their jobs are still running and need to
> be killed by sending the kill signal.  The job should also die with
> the session if it is running in the foreground.
That sounds like a session management issue which should be unrelated to
Lustre.

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100618/ec27feda/attachment.bin