> On Nov. 29, 2016, 3:08 p.m., Neil Conway wrote: > > I'd still like to see more discussion of how someone might actually use > > this feature. For example, when you say "With these constraints operators > > can use a > > global hard limit to contain resource limits set by users" -- how would the > > operator do this? Presumably the operator cannot enforce global resource > > limits via a user-specified flag in `ContainerInfo`. > > Benjamin Bannier wrote: > This section is related to POSIX resource limits in particular, and not > how they are mapped in Mesos. I specifically mention _POSIX resource limit_ > at the beginning of the paragraph, and also replaced _operator_ with _system > administrators_ to make this clearer.
Sure. I still think that there should be more discussion of how to use this feature to solve an actual problem that a cluster operator or user might encounter. - Neil ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/53982/#review157254 ----------------------------------------------------------- On Dec. 5, 2016, 10:14 a.m., Benjamin Bannier wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/53982/ > ----------------------------------------------------------- > > (Updated Dec. 5, 2016, 10:14 a.m.) > > > Review request for mesos, Jie Yu and Neil Conway. > > > Bugs: MESOS-6427 > https://issues.apache.org/jira/browse/MESOS-6427 > > > Repository: mesos > > > Description > ------- > > Added documentation for posix/rlimit isolator. > > > Diffs > ----- > > docs/mesos-containerizer.md 2bff35f6361f760a9001a249d2c01bbbc9e72932 > docs/posix_rlimits.md PRE-CREATION > > Diff: https://reviews.apache.org/r/53982/diff/ > > > Testing > ------- > > Tested with github markdown renderer, and with build setup from `site/`. > > > Thanks, > > Benjamin Bannier > >
