[
https://issues.apache.org/jira/browse/HDDS-14510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-14510:
-------------------------------
Description:
Currently, we uses OM node ID to uniquely identify OMs. For example
* OM might return the suggested leader OM node ID.
* Transfer leadership uses OM node
However, the main issue is that the client OM node IDs and server OM node IDs
might be different and there is currently no way to enforce this.
Example (OM service with 10.0.0.1, 10.0.0.2, 10.0.0.3)
Client configuration
* om4: 10.0.0.1
* om5: 10.0.0.2
* om6: 10.0.0.3
Server configuration
* om1: 10.0.0.1
* om2: 10.0.0.2
* om3: 10.0.0.3
In this setup, if the OM server says that the suggested leader ID is om2,
client will not be able to recognize it since om2 does not exist in the
configuration.
We should use OM ID instead. GetServiceList will return the OM ID on top of the
OM node ID. Client can still use the OM node ID, but once it gets the OM ID of
the whole OM service, it should use that OM ID. Suggested leader ID should use
OM ID so that it will be useful.
was:
Currently, we uses OM node ID to uniquely identify OMs. For example
* OM might return the suggested leader OM node ID.
* Transfer leadership uses OM node
However, the main issue is that the client OM node IDs and server OM node IDs
might be different and there is currently no way to enforce this.
Example (OM service with 10.0.0.1, 10.0.0.2, 10.0.0.3)
Client configuration
* om4: 10.0.0.1
* om5: 10.0.0.2
* om6: 10.0.0.3
Server configuration
* om1: 10.0.0.1
* om2: 10.0.0.2
* om3: 10.0.0.3
In this setup, if the OM server says that the suggested leader ID is om2,
client will not be able to recognize it since om2 does not exist in the
configuration.
We should use OM ID instead. GetServiceList will return the OM ID, on top of
the OM node ID. Client can still use the OM node ID, but once it gets the OM ID
of the whole OM service, it should use that OM ID. Suggested leader ID should
use OM ID so that it will be useful.
> Use OM ID instead of OM Node ID for suggested leader
> ----------------------------------------------------
>
> Key: HDDS-14510
> URL: https://issues.apache.org/jira/browse/HDDS-14510
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> Currently, we uses OM node ID to uniquely identify OMs. For example
> * OM might return the suggested leader OM node ID.
> * Transfer leadership uses OM node
> However, the main issue is that the client OM node IDs and server OM node IDs
> might be different and there is currently no way to enforce this.
> Example (OM service with 10.0.0.1, 10.0.0.2, 10.0.0.3)
> Client configuration
> * om4: 10.0.0.1
> * om5: 10.0.0.2
> * om6: 10.0.0.3
> Server configuration
> * om1: 10.0.0.1
> * om2: 10.0.0.2
> * om3: 10.0.0.3
> In this setup, if the OM server says that the suggested leader ID is om2,
> client will not be able to recognize it since om2 does not exist in the
> configuration.
> We should use OM ID instead. GetServiceList will return the OM ID on top of
> the OM node ID. Client can still use the OM node ID, but once it gets the OM
> ID of the whole OM service, it should use that OM ID. Suggested leader ID
> should use OM ID so that it will be useful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
