You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Pratyush Bhatt (Jira)" <ji...@apache.org> on 2023/06/11 08:21:00 UTC

[jira] [Updated] (KNOX-2917) [Ozone-Knox] Port blocking on one SCM Instance blocks all the SCM UI Nodes

     [ https://issues.apache.org/jira/browse/KNOX-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pratyush Bhatt updated KNOX-2917:
---------------------------------
    Attachment:     (was: image (9).png)

> [Ozone-Knox] Port blocking on one SCM Instance blocks all the SCM UI Nodes
> --------------------------------------------------------------------------
>
>                 Key: KNOX-2917
>                 URL: https://issues.apache.org/jira/browse/KNOX-2917
>             Project: Apache Knox
>          Issue Type: Bug
>            Reporter: Pratyush Bhatt
>            Priority: Major
>
> ozone.scm.https-port is set as 9877
> Blocked the port on one of the SCM Instance
> {noformat}
> [root@ozn-kx4-3 ~]# sudo iptables -L
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
> [root@ozn-kx4-3 ~]# sudo iptables -A INPUT -p tcp --dport 9877 -j DROP
> [root@ozn-kx4-3 ~]# sudo iptables -L
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> DROP       tcp  --  anywhere             anywhere             tcp dpt:9877
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination{noformat}
> The affected node is getting 500, which is correct, but along with that other two SCM Instances are also throwing the same even when the port is not blocked there.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)