I think that would be a cool addition to the API, and relatively easy to implement. I'd be happy to shepherd if you are willing to take a crack at a patch!
On Tue, Jan 12, 2016 at 2: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. > > Thanks :-) > Brian >
