Hexiaoqiao commented on PR #6183: URL: https://github.com/apache/hadoop/pull/6183#issuecomment-1827820008
Thanks @gp1314 and @xinglin for your works. I am not very sure to get the total purpose here. > In the case of configuring 3 journal nodes in HDFS, if only 2 journal nodes are available and 1 journal node fails to start due to machine issues, it will result in a long initialization time for the namenode (around 30-40 minutes, depending on the IPC timeout and retry policy configuration). Do you mean that NameNode restart will cost extra over 30~40 minutes while 1/3 JN could not be available? It is interesting where it costs? IIUC, The majority JN work well, it will connect and interact well. > The failed journal node cannot recover immediately, but HDFS can still function in this situation. In our production environment, we encountered this issue and had to reduce the IPC timeout and adjust the retry policy to accelerate the namenode initialization and provide services. I used to maintain JNs online one by one, but didn't meet timeout at NameNode side. Not sure what different between them, one point is the version could have some differences(our version is based on 2.7.1 with some internal improvement.) Thanks again. Please correct me if I missed something. -- 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: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
