<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">Le lun. 28 nov. 2016 à 17:34, Neil Gilmore <<a href="mailto:ngilmore@grammatech.com">ngilmore@grammatech.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
Hi Pierre,<br class="gmail_msg">
<br class="gmail_msg">
Thanks for the confirmation. Please note, because I failed to
mention it, that we set collapseRequests globally for most
schedulers.<br class="gmail_msg">
<br class="gmail_msg">
Our fix ended up being to append the master name to the schedulers.
We lose failover for the schedulers, though.<br class="gmail_msg">
<br class="gmail_msg">
I may look at your solution if I get some time. I may not understand
correctly, but it sounds like I'd end up with a builder with the
same name on 2 different masters. One would be the actual builder,
and the other would exist solely for its collapseRequests behavior?<br class="gmail_msg"></div></blockquote><div>Indeed, this is the case for 2 masters.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
<br class="gmail_msg">
It would seem that an eventual fix would involve using the collapse
behavior attached specifically to a builder, if present. If not
present, the global config would be able to use the default
function, given function, or nothing. I don't think it would be too
hard to implement that. The only oddity right now is that scheduling
has to jump through the builder to find the function.</div></blockquote><div><br></div><div>I guess the real fix would be to attach the collapseRequest behaviour to the schedulers rather than the builders (and mark the builder one deprecated)</div><div>It would be imho too complicated to make it work by sending message to the builder to run the collapse algorithm.</div><div>Pierre</div></div></div>