[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Quill Question
- Date: Mon, 16 Feb 2009 14:37:30 -0500
- From: "Natarajan, Senthil" <senthil@xxxxxxxx>
- Subject: Re: [Condor-users] Quill Question
Thanks for your response.
Is it possible to start quill daemon (condor_quilld) on all the nodes remotely from the central manager machine.
Even though DAEMON_LIST doesn't have QUILL. If that's not possible.
Is there any way we can remotely configure and start condor_quill daemon on all the nodes from central manager.
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Erik Paulson
Sent: Wednesday, February 11, 2009 1:17 PM
To: Condor-Users Mail List
Subject: Re: [Condor-users] Quill Question
Yes, it's working the way it's supposed to work.
For each machine that you want to appear in the database, you need to run
a condor_quilld on that machine. So, if you have a 100 node pool, and you
want the machines_horizontal table to have data frmo all execute nodes, you
need to run 100 quill daemons.
You only need one instance of a postgres database, and only one condor_dbmsd
per Condor pool.
On Tue, Feb 10, 2009 at 04:33:19PM -0500, Natarajan, Senthil wrote:
> I configured Quill demon to run on Central Manager, I can get all the info about the Jobs from the Quill Database.
> But the table "machines_horizontal" has only the central manager node info, none of the other machines info are available.
> Is it because only central manager is running the quill daemon and hence other machines info are not updated in the table.
> Is this is the way it suppose to work? Is it possible to get the table (machines_horizontal) updated with the same number of nodes info as condor_status gives?
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at:
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: