Another thought here.
Maybe the usage method can have a second polymorph by:
usage(Executor_State)
to collect usage for executor of one specific state, like RUNNING.
This will make the caller more easily to use the API without anymore
filtering.
Any comments would be welcome!
On 2016/3/2 14:01, Du, Fan wrote:
When Qos controller make estimations and corrections based on current
slave executor usages,
the current schema in ResourceUsage does not include executor state,
IMO,the usages only useful
for estimating resource slack and applying corrections is from RUNNING
executors, MESOS-4753
is created for this without any feedback, pls correct me if I missed
something obvious.
Thanks