[
https://issues.apache.org/jira/browse/HDDS-2162?focusedWorklogId=318529&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-318529
]
ASF GitHub Bot logged work on HDDS-2162:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Sep/19 19:42
Start Date: 25/Sep/19 19:42
Worklog Time Spent: 10m
Work Description: arp7 commented on pull request #1511: HDDS-2162. Make
Kerberos related configuration support HA style config.
URL: https://github.com/apache/hadoop/pull/1511#discussion_r328305846
##########
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/ha/OMHANodeDetails.java
##########
@@ -0,0 +1,309 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with this
+ * work for additional information regarding copyright ownership. The ASF
+ * licenses this file to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * <p>
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * <p>
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,WITHOUT
+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ * License for the specific language governing permissions and limitations
under
+ * the License.
+ */
+
+package org.apache.hadoop.ozone.om.ha;
+
+import com.google.common.base.Preconditions;
+import org.apache.hadoop.hdds.conf.OzoneConfiguration;
+import org.apache.hadoop.net.NetUtils;
+import org.apache.hadoop.ozone.OmUtils;
+import org.apache.hadoop.ozone.OzoneConsts;
+import org.apache.hadoop.ozone.OzoneIllegalArgumentException;
+import org.apache.hadoop.ozone.om.OMConfigKeys;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.net.InetSocketAddress;
+import java.util.ArrayList;
+import java.util.Collection;
+import java.util.List;
+
+import static org.apache.hadoop.ozone.om.OMConfigKeys.OZONE_OM_ADDRESS_KEY;
+import static org.apache.hadoop.ozone.om.OMConfigKeys.OZONE_OM_NODES_KEY;
+import static org.apache.hadoop.ozone.om.OMConfigKeys.OZONE_OM_NODE_ID_KEY;
+import static
org.apache.hadoop.ozone.om.OMConfigKeys.OZONE_OM_RATIS_PORT_DEFAULT;
+import static org.apache.hadoop.ozone.om.OMConfigKeys.OZONE_OM_RATIS_PORT_KEY;
+import static org.apache.hadoop.ozone.om.OMConfigKeys.OZONE_OM_SERVICE_IDS_KEY;
+
+/**
+ * Class which maintains peer information and it's own OM node information.
+ */
+public class OMHANodeDetails {
+
+ public static final Logger LOG =
+ LoggerFactory.getLogger(OMHANodeDetails.class);
+ private final OMNodeDetails localNodeDetails;
+ private final List<OMNodeDetails> peerNodeDetails;
+
+ public OMHANodeDetails(OMNodeDetails localNodeDetails,
+ List<OMNodeDetails> peerNodeDetails) {
+ this.localNodeDetails = localNodeDetails;
+ this.peerNodeDetails = peerNodeDetails;
+ }
+
+ public OMNodeDetails getLocalNodeDetails() {
+ return localNodeDetails;
+ }
+
+ public List< OMNodeDetails > getPeerNodeDetails() {
+ return peerNodeDetails;
+ }
+
+
+ /**
+ * Inspects and loads OM node configurations.
+ *
+ * If {@link OMConfigKeys#OZONE_OM_SERVICE_IDS_KEY} is configured with
+ * multiple ids and/ or if {@link OMConfigKeys#OZONE_OM_NODE_ID_KEY} is not
+ * specifically configured , this method determines the omServiceId
+ * and omNodeId by matching the node's address with the configured
+ * addresses. When a match is found, it sets the omServicId and omNodeId from
+ * the corresponding configuration key. This method also finds the OM peers
+ * nodes belonging to the same OM service.
+ *
+ * @param conf
+ */
+ public static OMHANodeDetails loadOMHAConfig(OzoneConfiguration conf) {
+ InetSocketAddress localRpcAddress = null;
+ String localOMServiceId = null;
+ String localOMNodeId = null;
+ int localRatisPort = 0;
+ Collection<String> omServiceIds = conf.getTrimmedStringCollection(
+ OZONE_OM_SERVICE_IDS_KEY);
+
+ String knownOMNodeId = conf.get(OZONE_OM_NODE_ID_KEY);
Review comment:
Isn't there also a key for our own service ID?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 318529)
Time Spent: 40m (was: 0.5h)
> Make Kerberos related configuration support HA style config
> -----------------------------------------------------------
>
> Key: HDDS-2162
> URL: https://issues.apache.org/jira/browse/HDDS-2162
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> To have a single configuration to use across OM cluster, few of the configs
> like
> OZONE_OM_KERBEROS_KEYTAB_FILE_KEY,
> OZONE_OM_KERBEROS_PRINCIPAL_KEY,
> OZONE_OM_HTTP_KERBEROS_KEYTAB_FILE,
> OZONE_OM_HTTP_KERBEROS_PRINCIPAL_KEY need to support configs which append
> with service id and node id.
>
> Addressed OM_DB_DIRS, OZONE_OM_ADDRESS_KEY also in this patch.
>
> This Jira is to fix the above configs.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
