Re: [p4] p4 monitor terminate never seems to work

I found this old thread and decided to add my 0.02 to it.

I can't say "p4 monitor terminate" never works for us now - I've seen some processes go away.
But not all.

Here's an example -- this is on an edge server:
-> p4 -p 1666 monitor show -l 
 2305 T mmirman    181:31:14 obliterate -ah //tasks/...Bhs.../...
[snip]

Yes, I tried to terminate this process, which - if I recall correctly - was hung for a while and I decided I didn’t need to run it against an edge anyway.
P4 *marked* the process for termination, but that's it.
Sure enough, "ps" shows that process still running since November 3 - even though:

-> p4 -p 1666 configure show db.monitor.interval
db.monitor.interval:30 (configure)

This is for
Server version: P4D/LINUX26X86_64/2017.1/1534792 (2017/07/26)

--
Michael Mirman
MathWorks, Inc.
508-647-7555

-----Original Message-----
From: perforce-user [mailto:[email protected]] On Behalf Of Sambwise
Sent: Wednesday, October 18, 2017 2:35 PM
To: [email protected]
Subject: Re: [p4] p4 monitor terminate never seems to work

Posted on behalf of forum user 'Sambwise'.

I haven't played with db.monitor interval, but from the description of it in
the KB article:

p4 configure set db.monitor.interval=30


which, for new commands processed by the server going forward, configures the
server to check for and terminate processes that have had  p4 monitor terminate
run  on them and are blocked on client input.   it sounds like it's checking
for commands that are in a very specific state, i.e. waiting on a client request
to complete (and it might be even more specific than that, e.g. it's
checking client-EditData requests but not, say, client-ReconcileAdd).

If you're able to track down the client that's running this reconcile
and do more investigation it might be possible to figure out exactly what
it's doing (if anything -- it wouldn't shock me if the client has in
fact gone away and the server somehow lost track of it).  If it's
a case of the reconcile command being really performance-intensive (e.g.
you've got a hundred potentially-renamed files that are all near matches for
each other and it's in combinatoric hell) that should be pretty easy to
diagnose/reproduce, and you can fix it going forward by tweaking configurables
to either make reconcile less fastidious or lower whatever other threshold is
currently set too high.



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/3581-p4-monitor-terminate-never-seems-to-work
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user