[
https://issues.apache.org/jira/browse/HDDS-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chung En Lee updated HDDS-4819:
-------------------------------
Target Version/s: 2.2.0
2.2.0 (was: 2.1.0)
<<Bulk update>>
Apache Ozone 2.1.0 release is in progress. I'm updating all unresolved jiras
targeting 2.1.0 to retarget 2.2.0.
> Configuration property for OM to define bind address
> ----------------------------------------------------
>
> Key: HDDS-4819
> URL: https://issues.apache.org/jira/browse/HDDS-4819
> Project: Apache Ozone
> Issue Type: Improvement
> Components: OM
> Affects Versions: 1.0.0, 1.1.0
> Reporter: UENISHI Kota
> Assignee: UENISHI Kota
> Priority: Major
> Labels: pull-request-available
>
> Currently, "OZONE_OM_ADDRESS_KEY" (="ozone.om.address") is used both for
> client side and for server side. This is nice for unifying configuration
> files in both clients and servers, but in case where OM has multiple IP
> addresses and want to bind "0.0.0.0", the config file cannot be naively
> copied for clients' usage.
> I would suggest adding another config key such as "ozone.om.bind-host" as
> well as "ozone.om.https-bind-host" .
> I'm not sure there were any discussion on this topic, but I'd welcome a
> pointer to any past discussion.
> Situation will be more complicated when OM HA is enabled. Say OM HA consists
> of om1, om2, om3 and service id is "sid". om1 config will be like:
> {quote}ozone.om.address.sid.om1=0.0.0.0
> ozone.om.address.sid.om2=om2
> ozone.om.address.sid.om3=om3{quote}
> om2:
> {quote}ozone.om.address.sid.om1=om1
> ozone.om.address.sid.om2=0.0.0.0
> ozone.om.address.sid.om3=om3{quote}
> om3:
> {quote}ozone.om.address.sid.om1=om1
> ozone.om.address.sid.om2=om2
> ozone.om.address.sid.om3=0.0.0.0{quote}
> clients:
> {quote}ozone.om.address.sid.om1=om1
> ozone.om.address.sid.om2=om2
> ozone.om.address.sid.om3=om3{quote}
> It'll be a hustle to generate different configurations for all 4 roles.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
