Hi Doug:
On 1/31/08, Doug Nordwall <[EMAIL PROTECTED]> wrote:
> 1) replace the _value_ with the value of the job_id, and modifying the
> code so that you can update the location. This would also include the
> option to keep the location as it is written currently, or spoof it
> with a job_id (or arbitrary value)
I'm a bit unsure about the "location" you are referring to here. Are
you talking about the location field from gmond.conf:
The host section provides information about the host running this
instance of gmond. Currently only the
location string attribute is supported. Example:
host {
location = "1,2,3"
}
The numbers represent Rack, Rank and Plane respectively.
?
> 2) add a new field to the HOST entry called job_id and allow it to be
> updated without restarting ganglia.
>
> Sadly, we can't use a job_id a metric (well, we could but it's more of
> a pain in other part of our code). For the purposes of our machine, a
> machine is dedicated to a single job. The ultimate idea is to be able
> to drop whatever we like into that host field and have it change
> without an entire restart of ganglia.
When you talk about job, I think about schedulers -- are you running
something like PBS/SGE?
Anyways, couldn't you just inject this "job_id" metric using gmetric
by querying your scheduler database (assuming you're running one) and
figuring out the id of the job that's running on the host at any given
time?
Cheers,
Bernard
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ganglia-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general
