gp1314 opened a new pull request, #6183:
URL: https://github.com/apache/hadoop/pull/6183

   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   
   * 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). 
   * 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'm wondering if it would be possible to have a journal node maintenance 
list to speed up the namenode initialization knowing that one journal node 
cannot provide services in advance?
   
   ### How was this patch tested?
   unit test.
   
   
   ### For code changes:
   
   - [x] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   


-- 
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]

Reply via email to