Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Condor Watch Queue Announcement
- Date: Tue, 08 Dec 2020 14:30:00 +0000
- From: "Bockelman, Brian" <BBockelman@xxxxxxxxxxxxx>
- Subject: Re: [HTCondor-users] Condor Watch Queue Announcement
Hi David,
Instead of a backport, would a user-level install be acceptable?
That is, would it be possible to do a "pip install htcondor" to get the right python tools and then copy condor_watch_q from the source. Something like this:
$ virtualenv-3 watchq
Using base prefix '/usr'
New python executable in /home/cse496/bbockelm/tmp/test_watch_q/watchq/bin/python3
Also creating executable in /home/cse496/bbockelm/tmp/test_watch_q/watchq/bin/python
Installing setuptools, pip, wheel...done.
[bbockelm@hcc-briantest7 test_watch_q]$ . watchq/bin/activate
(watchq) $ pip3 install htcondor
Collecting htcondor
Downloading htcondor-8.9.10-cp36-cp36m-manylinux1_x86_64.whl (31.7 MB)
|ââââââââââââââââââââââââââââââââ| 31.7 MB 189 kB/s
Installing collected packages: htcondor
Successfully installed htcondor-8.9.10
(watchq) $ curl 'https://raw.githubusercontent.com/htcondor/htcondor/960808a1dc83ad0a272034d7440f1af53ad6d81d/src/condor_scripts/condor_watch_q'
> ./condor_watch_q
$ python condor_watch_q -h
usage: condor_watch_q [-help] [-debug] [-users USER [USER ...]]
[-clusters CLUSTER_ID [CLUSTER_ID ...]]
[-files FILE [FILE ...]]
[-batches BATCH_NAME [BATCH_NAME ...]]
[-collector COLLECTOR] [-schedd SCHEDD]
[-exit GROUPER,JOB_STATUS[,EXIT_STATUS]]
[-groupby {batch,log,cluster}] [-table] [-progress]
[-row-progress] [-summary]
[-summary-type {totals,percentages}] [-updated-at]
[-abbreviate] [-color] [-refresh]
Track the status of jobs over time without repeatedly querying the condor_schedd.
....
It's not the prettiest solution but might get you going in a pinch.
Brian
> On Dec 8, 2020, at 6:02 AM, David Cohen <cdavid@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Hi,
> condor_status -submitter
> Gives very partial understanding on how much the cluster is utilized, as there is no way to know from it how many of the jobs are multicore, if any.
>
> There is an unmaintained tool "condor_wn" that gives summary tables, I was hoping to find a way to accomplish the same with an integrated tool.
>
> https://indico.cern.ch/event/686369/contributions/2815630/attachments/1583413/2502661/Htcondor_-_condor_wn.pdf
>
> -David
>
>
> On Mon, Dec 7, 2020 at 7:07 PM Greg Thain <gthain@xxxxxxxxxxx> wrote:
>
>
>> Hi,
>>
>> Is there a chance that condor_watch_q will be backported to the 8.8 branch?
>>
>> I'm in the process of migrating from torque to HTCondor and I'm missing a tool like that to get overall status of system load.
>>
>> Today I'm using an homemade script that displays other the number of jobs, also how many cores and memory are requested by the jobs:
>>
> It doesn't show all the information your current script shows, but you may also want to consider
>
> condor_status -submitter
>
> which is a quick way to get running/idle/held job counts per submitter.
>
> -greg
>
> _______________________________________________
> 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/
> _______________________________________________
> 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/