[ Jeff's posts aren't getting to the list, so I'm reposting. -Chris ]
Date: Mon, 18 Dec 2006 15:32:08 -0500 From: Jeff Squyres <[EMAIL PROTECTED]> To: Chris Dunlap <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: Re: [munge-users] munged running at 100% Actually, I was only testing on two back-end nodes (separately, at different times) before deploying it on all of them. So I don't think it's an overloading problem. The head node runs the whole gid has map routine in 15-30 seconds -- the back-end nodes seem to take *much* longer than that (I verified this with a standalone C program that essentially duplicates what the gid hash map routine does -- looping over getgrent(), etc.). So I think that this is some kind of not-related-to-munge configuration problem on my part. I'm trying to track that down now. (FWIW, I don't think my post made it to the list again -- you got it because I did "reply all" and therefore you were CC'ed) On Dec 18, 2006, at 3:25 PM, Chris Dunlap wrote: > I wonder if part of the problem is with the gids map updating on > all of the back-end nodes at the same time, and the NIS service is > getting hammered. > > -Chris > > > On Mon, 12/18/06 03:06p EST, Jeff Squyres wrote: >> >> - I put some printf's in the code to show that the gid lookup for the >> hash map does seem to be the culprit; the getgrent function runs >> *much* faster on the head node than my compute nodes (suggesting some >> kind of not-related-to-munge configuration problem on my compute >> nodes -- I'm investigating). -- Jeff Squyres Server Virtualization Business Unit Cisco Systems _______________________________________________ munge-users mailing list [EMAIL PROTECTED] https://mail.gna.org/listinfo/munge-users
