simbadzina commented on code in PR #4441: URL: https://github.com/apache/hadoop/pull/4441#discussion_r898588205
########## hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/RouterGSIContext.java: ########## @@ -0,0 +1,56 @@ +/** + * 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 + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * 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.hdfs.server.federation.router; + +import org.apache.hadoop.classification.InterfaceAudience; +import org.apache.hadoop.classification.InterfaceStability; +import org.apache.hadoop.hdfs.ClientGSIContext; +import org.apache.hadoop.ipc.protobuf.RpcHeaderProtos.RpcRequestHeaderProto; + +/** + * Global State ID context for the router. + * <p> + * This is the router side implementation responsible for receiving + * state alignment info from server(s). + */ [email protected] [email protected] +public class RouterGSIContext extends ClientGSIContext { Review Comment: I feel the alignment between routers and namenode can be taken care of with just ClientGSIContext. How does the router not updating the lastSeenStateID when communicating with the namenode help? ########## hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/ConnectionManager.java: ########## @@ -231,6 +246,18 @@ public ConnectionContext getConnection(UserGroupInformation ugi, return conn; } + /** + * Dynamically reconfigure the enableObserverRead. + */ + public void reconfEnableObserverRead(boolean enableObserverRead) { + readLock.lock(); + this.enableObserverRead = enableObserverRead; + for (RouterGSIContext routerGSIContext : alignmentContexts.values()) { + routerGSIContext.setEnableObserverRead(enableObserverRead); + } + readLock.unlock(); + } + Review Comment: Why do we need to reconfigure observer reads dynamically? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
