For the records: According to
http://www.globus.org/toolkit/docs/5.2/5.2.0/gram5/rn/#gram5-fixed
it's a bug and fixed in 5.2...
On 10/12/11 12:12 PM, Martin Feller wrote:
Hi Globus team,
GT version: 5.0.4
jglobus version: 1.8.0
When I submit a job using jglobus' Gram API, the globus-job-manager
processes seem to accumulate open files.
It looks like, for each job, the job manager opens files for the
stdout and stderr params in the job description (or /dev/null if not
specified) and doesn't close them, even if the job is done, until the
job manager shuts down.
This becomes problematic if you have active users submitting a lot of
jobs.
Any ideas what would cause the job manager to keep these files open?
NOTE: The job manager does not accumulate open files if I submit a job
using the C client globusrun.
I attached output from lsof as example after submitting 5 sequential
jobs. stdout and stderr params of the jobs were
/home/testuser/[out|err]_<UUID>. The jobs were simple /bin/hostname
jobs and done when I took the lsof snapshot.
Thanks!
Martin
