[jira] [Commented] (MESOS-5337) Add Master Flag to enable fine-grained filtering of HTTP endpoints.
[ https://issues.apache.org/jira/browse/MESOS-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15275145#comment-15275145 ] Joerg Schad commented on MESOS-5337: Then we still incur the performance penalty. But if acls are permissive it would mean that the user cannot see any frameworks/tasks... I will add a warning in that case. > Add Master Flag to enable fine-grained filtering of HTTP endpoints. > --- > > Key: MESOS-5337 > URL: https://issues.apache.org/jira/browse/MESOS-5337 > Project: Mesos > Issue Type: Improvement >Reporter: Joerg Schad >Assignee: Joerg Schad > > As the fine-grained filtering of endpoints can the rather expensive, we > should create a master flag to enable/disable this feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5337) Add Master Flag to enable fine-grained filtering of HTTP endpoints.
[ https://issues.apache.org/jira/browse/MESOS-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274991#comment-15274991 ] Adam B commented on MESOS-5337: --- What happens when --endpoint_authorization_filtering is enabled, but there is no such ACL configured? I assume we still incur the performance penalty? What happens when --endpoint_authorization_filtering is disabled, but the filtering ACLs are configured? No filtering? A warning somewhere? > Add Master Flag to enable fine-grained filtering of HTTP endpoints. > --- > > Key: MESOS-5337 > URL: https://issues.apache.org/jira/browse/MESOS-5337 > Project: Mesos > Issue Type: Improvement >Reporter: Joerg Schad >Assignee: Joerg Schad > > As the fine-grained filtering of endpoints can the rather expensive, we > should create a master flag to enable/disable this feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
