> On Jan. 28, 2014, 6:31 a.m., David Robinson wrote: > > src/master/http.cpp, line 349 > > <https://reviews.apache.org/r/17442/diff/2/?file=452628#file452628line349> > > > > s/launched_tasks/launched_tasks_gauge/ ? (or active_tasks_gauge, please > > yourself) > > > > All the other *_tasks are counters, which, but calling this > > something_tasks also implies it is. This isn't a counter so it's better to > > explicitly call it something else, such as something_tasks_gauge.
There are lots of stats that we currently expose that are gauges but we don't explicitly call them that way. I agree adding a suffix like "_gauge" is more explicit but maybe we should do that across all gauge stats in one fell swoop to avoid confusion? What do you think? - Vinod ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/17442/#review32962 ----------------------------------------------------------- On Jan. 28, 2014, 2:59 a.m., Vinod Kone wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/17442/ > ----------------------------------------------------------- > > (Updated Jan. 28, 2014, 2:59 a.m.) > > > Review request for mesos, Benjamin Hindman, Ben Mahler, David Robinson, and > Niklas Nielsen. > > > Bugs: MESOS-772 > https://issues.apache.org/jira/browse/MESOS-772 > > > Repository: mesos-git > > > Description > ------- > > See summary. > > I opted for "active" tasks instead of "running" tasks because I didn't want > the stats endpoint to loop through all tasks to figure out if a task is in > RUNNING state. I think "active" is useful for most debugging purposes. > > > Diffs > ----- > > src/master/http.cpp 546e91dbb9c8ee1014bb4f0b3be2714ad6a2d520 > > Diff: https://reviews.apache.org/r/17442/diff/ > > > Testing > ------- > > make check > > > Thanks, > > Vinod Kone > >
