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] [Updated] (HDDS-8805) [Ozone-Knox] Port blocking on one OM Instance blocks all the OM UIs
[ https://issues.apache.org/jira/browse/HDDS-8805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pratyush Bhatt updated HDDS-8805:
---------------------------------
Component/s: Ozone Manager
> [Ozone-Knox] Port blocking on one OM Instance blocks all the OM UIs
> -------------------------------------------------------------------
>
> Key: HDDS-8805
> URL: https://issues.apache.org/jira/browse/HDDS-8805
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Manager
> Reporter: Pratyush Bhatt
> Priority: Major
> Attachments: image (6).png, image (7).png, image (8).png
>
>
> ozone.om.https-port is set to 9875
> Blocked the port on one of the OM 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 9875 -j DROP
> [root@ozn-kx4-3 ~]# sudo iptables -L
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
> DROP tcp -- anywhere anywhere tcp dpt:sapv1
> Chain FORWARD (policy ACCEPT)
> target prot opt source destination
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination{noformat}
> The affected node UI is getting 500, which is correct, but along with that other two OM UI 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