+1 to this feature! We have always wanted something like this but never had bandwidth to pull it off.
On Tue, Jan 12, 2016 at 3:14 PM, John Sirois <[email protected]> wrote: > > > On Tue, Jan 12, 2016 at 3:56 PM, Brian Hatfield <[email protected]> > wrote: >> >> Hi, >> >> We currently run a (relatively) small Mesos/Aurora cluster, and don't >> always have significant resource overhead available. >> >> Sometimes, we go to schedule a job and we're just short of what we >> estimated-by-hand we'd need in the cluster for it. Most of the tasks >> schedule - but a few stay "PENDING" because of the resource constraint. This >> often confuses users, or in some cases, causes the command to block for a >> while until it eventually times out. >> >> We're currently working on automating somewhat-more-precise basic >> estimation with information sourced from /offers to get a sense of "nope, >> your task won't schedule" to provide fast feedback that doesn't manipulate >> the state of the cluster. >> >> A friend recommended that I suggest to this mailing list something >> integrated into Aurora to accomplish this instead - since our basic >> estimation doesn't include co-scheduling constraints, quotas, etc. >> >> So: We believe that this feature doesn't exist in Aurora today, and wanted >> to suggest it as a future feature for the project. > > > I think this would be a great feature from simple yes/no to more > sophisticated likelyhood estimates even based on time of day (cron job > scheduling taken into account): > 1. A ticket [1] describing the minimum viable feature. > 2. Work towards implementation [2]. > > Would you be willing to do any of these? I'd be willing to review designs > and reviews. > > [1] https://issues.apache.org/jira/secure/CreateIssue!default.jspa > [2] http://aurora.apache.org/documentation/latest/contributing/ > >> >> Thanks :-) >> Brian > >
