Thanks Steve and all, for the explanation. I don't think I really
need to log the startd info.
At the moment, I'm running QUILL daemon on the Central Manager and
the Submit host, and DBMSD only on the Central Manager - is this
correct (well, in my case) way of running Quill? Even though I can
run condor_q, I don't get any answer back when I run condor_history
with "-completedsince":
[root@serv07 JobManager]# condor_history -completedsince ’01/01/2011 13:00’
-- Quill: quill@xxxxxxxxxxxxxxxxxxxxxxxx : <vserv03:5432> : quill_vserv03
ID OWNER SUBMITTED RUN_TIME ST COMPLETED CMD
No historical jobs in the database match your query
Does it mean Quill is not logging anything at all?
Cheers,
Santanu
On 08/01/11 01:57, Steven Timm wrote:
On Sat, 8 Jan 2011, Santanu Das wrote:
Thanks Erik and Wancheng, for pointing out
the DBMSD bit - it's fixed now.
Two points:
1. You should only run the DBMSD on one machine. The manual
says: "One machine should run the condor_dbmsd daemon. On this
machine, add it to the DAEMON_LIST configuration variable. All
Quill-enabled machines should also run the condor_quill
daemon. The machine running the condor_dbmsd daemon can also
run a condor_quill daemon."
One question: What do you mean "Quill-enabled machines"? Does it
mean all the Execute nodes? If yes, what's the benefit running
QUILL on every single node?
The only reason you would run Quill on every single node is if you
are keeping track of all the startd information in quill. The
more
common configuration is only to run on the nodes that have a
schedd.
If you are keeping track of all daemon info in quill then you
need a huge database machine, there are some presentations in
condor weeks of 2007 and 2008 that describe just how big.
Steve Timm
Cheers,
Santanu
|