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

[jira] [Created] (HDDS-8806) Port blocking on one SCM Instance blocks all the SCM Nodes

Pratyush Bhatt created HDDS-8806:
------------------------------------

             Summary: Port blocking on one SCM Instance blocks all the SCM Nodes
                 Key: HDDS-8806
                 URL: https://issues.apache.org/jira/browse/HDDS-8806
             Project: Apache Ozone
          Issue Type: Bug
          Components: SCM
            Reporter: Pratyush Bhatt
         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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org