[
https://issues.apache.org/jira/browse/HDFS-16452?focusedWorklogId=748228&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-748228
]
ASF GitHub Bot logged work on HDFS-16452:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Mar/22 15:44
Start Date: 26/Mar/22 15:44
Worklog Time Spent: 10m
Work Description: hfutatzhanghb commented on pull request #3976:
URL: https://github.com/apache/hadoop/pull/3976#issuecomment-1079719195
> hi， @xkrogen . So sorry for disturbing you. I have a new idea about what
we have discussed. In practice, We usually plan some machines as Observer
Namenode before setup cluster. Can we add a configuration entry in
hdfs-site.xml to specify the nnid of Observer namenode ? After doing so, when
we initialize failoverProxy, we can aovid adding observer namenodes to the
proxies list. I am looking forward to your reply. Thx a lot.
hi，@xkrogen, could you please help me look at this problem? thanks a lot.
--
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]
Issue Time Tracking
-------------------
Worklog Id: (was: 748228)
Time Spent: 3h (was: 2h 50m)
> msync RPC should send to Acitve Namenode directly
> --------------------------------------------------
>
> Key: HDFS-16452
> URL: https://issues.apache.org/jira/browse/HDFS-16452
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namanode
> Affects Versions: 3.3.1
> Reporter: zhanghaobo
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 3h
> Remaining Estimate: 0h
>
> In current ObserverReadProxyProvider implementation, we use the following
> code to invoke msync RPC.
> {code:java}
> getProxyAsClientProtocol(failoverProxy.getProxy().proxy).msync(); {code}
> But msync RPC maybe send to Observer NameNode in this way, and then failover
> to Active NameNode. This can be avoid by applying this patch.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
