Issue #2118 has been updated by luke.

digant wrote:
> 
> Often, we are restarting puppetmaster when it is locked or dead or perhaps 
> hung on something it is processing.  How would this play with the idea of it 
> waiting for all connections/operations to finish?  Should we except to use a 
> hard kill instead?

If puppetmasterd is hung, then yes, you would expect to need to use a hard kill.

Hopefully, more closely tracking what requests are open and which are not 
returning would be a straightforward way to give us an idea of which requests 
are hanging, which should help us resolve those problems.
----------------------------------------
Bug #2118: Puppetmasterd should finish operations when restarting
http://projects.reductivelabs.com/issues/2118

Author: luke
Status: Accepted
Priority: Normal
Assigned to: luke
Category: plumbing
Target version: 0.26.0
Complexity: Unknown
Affected version: 0.24.7
Keywords: 


When the master gets a signal to restart, it will stop all open operations and 
restart immediately.  It should instead finish any of those operations before 
restarting.

I don't really know how this will work - I assume it will require some kind of 
registration process that keeps a counter of open connections, along with a 
lock that prevents new connections.  Thus, a restart will enable this lock, and 
will not restart until the number of open connections has dropped to 0.


----------------------------------------
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to