You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Santhosh Kumar Shanmugham (JIRA)" <ji...@apache.org> on 2017/03/20 20:26:41 UTC
[jira] [Commented] (MESOS-7266) Port-mapping isolator does not play
nice with external entities
[ https://issues.apache.org/jira/browse/MESOS-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933479#comment-15933479 ]
Santhosh Kumar Shanmugham commented on MESOS-7266:
--------------------------------------------------
https://reviews.apache.org/r/57765
> Port-mapping isolator does not play nice with external entities
> ---------------------------------------------------------------
>
> Key: MESOS-7266
> URL: https://issues.apache.org/jira/browse/MESOS-7266
> Project: Mesos
> Issue Type: Bug
> Components: agent, isolation
> Reporter: Santhosh Kumar Shanmugham
>
> Port-mapping isolator does not play nice with other entities working on the host that uses TrafficControl fitlers. Particularly, the isolator uses a blanket query to remove and replace filters for classifying ARP and ICMP packets. This causes the work done by other entities on the host to be mangled.
> Change the port-mapping isolator to behave well by limiting its updates to TC filters by specifying the filter handle, when updating/removing ICMP/ARP filters.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)