Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] identifying (gracefully/peacefully) shutting down daemons
- Date: Thu, 04 Aug 2016 14:54:46 -0500
- From: Brian Bockelman <bbockelm@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] identifying (gracefully/peacefully) shutting down daemons
Hi Thomas,
I donât know of any way to do this myself.
Note thereâs two levels here:
- Determining the state of the master. Is it trying to shut down daemons?
- Determining the state of the child daemons. Did they successfully get the signal from the master?
Brian
> On Aug 4, 2016, at 10:39 AM, Thomas Hartmann <thomas.hartmann@xxxxxxx> wrote:
>
> Hi all,
>
> I would like to find all daemons in my pool, that got a condor_off
> (-graceful -peaceful) and are draining and shutting down. So,
> is_owner/draining status is implied. Draining related ads are afais no
> positive indicator, since maybe the defragd would also initiates drainings.
>
>
> For the startd's I suppose
>
> Activity = Retiring
> ChildActivity = { "Retiring"
>
> would be the ads to check for.
>
> But I am not sure, if this is sufficient for identifying a node's
> daemon(s) shutting down compared to a job/slot preempting/draining for
> any reason where the daemons/slots(?) would be staying subsequently
> alive [1]?
>
> Cheers and thanks,
> Thomas
>
> [1]
> http://research.cs.wisc.edu/htcondor/manual/latest/3_5Policy_Configuration.html
>
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/