Issue #7225 has been updated by R.I. Pienaar. Parent task set to #7226
---------------------------------------- Feature #7225: mcollectived should be able to subscribe to a per identity queue https://projects.puppetlabs.com/issues/7225 Author: R.I. Pienaar Status: Ready For Testing Priority: Normal Assignee: R.I. Pienaar Category: Core Target version: 1.2.0 Keywords: Branch: ripienaar/feature/master/7225 Affected mCollective version: Topics are broadcast and not durable while queues are durable and point to point. Certain types of requests will make more sense point to point rather than broadcast: * Ones where discovery discovered just one node * Custom requests with just one expected reply * Perhaps even some threshold where p2p submission is prefered over broadcast submission like < 10 discovered hosts * Requests to agents that provide a service like Angelia, you could have n providers but any request will only be served by one agent not all * Requests that should be executed at any point when the daemon returns like for down hosts To enable all these kinds of use cases the nodes need to be able to subscribe to a queue each. To begin with we wont subscribe to a queue per server per collective just on the main collective as v.large amount of queues can have some pretty nasty scaling implications. There should also be options to purge the queue at startup if you never want to process commands that might have entered the queue after reboot/restart. -- 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://projects.puppetlabs.com/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.
