[
https://issues.apache.org/jira/browse/KNOX-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai moved HDDS-8806 to KNOX-2917:
----------------------------------------------
Component/s: (was: SCM)
Key: KNOX-2917 (was: HDDS-8806)
Workflow: no-reopen-closed, patch-avail (was: patch-available, re-open
possible)
Project: Apache Knox (was: Apache Ozone)
> [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
> 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)
