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

Pratyush Bhatt updated HDDS-8806:
---------------------------------
    Description: 
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.

  was:
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.

Test Cluster: [https://ozn-kx4-1.ozn-kx4.root.hwx.site:7183/cmf/home]


> [Ozone-Knox] Port blocking on one SCM Instance blocks all the SCM UI Nodes
> --------------------------------------------------------------------------
>
>                 Key: HDDS-8806
>                 URL: https://issues.apache.org/jira/browse/HDDS-8806
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: SCM
>            Reporter: Pratyush Bhatt
>            Priority: Major
>         Attachments: image (10).png, image (11).png, image (9).png
>
>
> 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)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to