Dan Leary created MESOS-10235:
---------------------------------
Summary: v1 Operator API GET_MASTER is missing
Capability.Type.QUOTA_V2
Key: MESOS-10235
URL: https://issues.apache.org/jira/browse/MESOS-10235
Project: Mesos
Issue Type: Bug
Components: HTTP API
Affects Versions: 1.11.0, 1.9.0
Environment: Ubuntu 18.04, Mesos 1.11.0 built from tarball.
Reporter: Dan Leary
A GET_MASTER call on the v1 HTTP Operator API at [http://master/api/v1] returns
a master_info that is missing Capability.Type.QUOTA_V2. E.g.:
{noformat}
{
"type" : "GET_MASTER",
"get_master" : {
"master_info" : {
"capabilities" : [
{
"type" : "AGENT_UPDATE"
},
{
"type" : "AGENT_DRAINING"
},
{}
], etc...
{noformat}
I suspect that this change to include/mesos/mesos.proto:
{noformat}
0bc857d672 ( Meng Zhu 2019-06-25 15:19:44 -0700 927)
0bc857d672 ( Meng Zhu 2019-06-25 15:19:44 -0700 928) //
The master can handle the new quota API, which supports setting
0bc857d672 ( Meng Zhu 2019-06-25 15:19:44 -0700 929) //
limits separately from guarantees (introduced in Mesos 1.9).
0bc857d672 ( Meng Zhu 2019-06-25 15:19:44 -0700 930)
QUOTA_V2 = 3;
{noformat}
Is also needed in include/mesos/v1/mesos.proto.
Consequently, enums org.apache.mesos.Protos.MasterInfo.Capability.Type and
org.apache.mesos.v1.Protos.MasterInfo.Capability.Type differ in the same
respect for those of us using protobufs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
