Issue #9409 has been updated by Matthaus Litteken. Status changed from Unreviewed to Accepted
Andrew, To clarify, your issue is that when running multiple dashboard nodes, if one dashboard has the yaml report, and the other node is processing the job, it won't find the report? ---------------------------------------- Bug #9409: DJ doesn't work in a multi-server environment https://projects.puppetlabs.com/issues/9409 Author: Andrew Forgue Status: Accepted Priority: Normal Assignee: Category: Target version: Keywords: Branch: Affected URL: Affected Dashboard version: 1.2.0 We are testing dashboard 1.2 and notice that it's use of delayed_jobs isn't bound to any node, therefore, if the YAML report isn't on the server that happened to start processing the job, the YAML file can't be found. There are 2 ways to rectify this: 1 - put the spool directory on NFS. I'd rather not introduce network dependency since if NFS goes away my reports are lost. 2 - Configure DJ to only process the import when the DJ detects the file, or on the same node that the job was scheduled. What is PuppetLabs desired action? This kind of seriously limits the scalability of the dashboard since now the spool directory must be shared among all the nodes. One server isn't enough to handle our load. -- 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.
