[ 
https://issues.apache.org/jira/browse/HDFS-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428772#comment-15428772
 ] 

Jiayi Zhou edited comment on HDFS-10702 at 8/19/16 8:35 PM:
------------------------------------------------------------

Upload a patch to fix some of the issues commented by Andrew. I haven't worked 
on the RpcHeader modification yet, want to see if the new patch runs properly 
first.

* Fix nitty issues. 
* Remove MethodCategory and use annotations instead. Add a new annotation 
ReadOnly.
* Idea of SyncInfo is also to add more fields in the future. 
NamenodeProtocol#getTransactionID is commented as NameNodeProtocol rather that 
ClientProtocol, so I add getSyncInfo() for ClientProtocol. Remove state from 
SyncInfo because we no longer need it. 


was (Author: clouderajiayi):
Upload a path to fix some of the issues commented by Andrew. I haven't worked 
on the RpcHeader modification yet, want to see if the new patch runs properly 
first.

* Fix nitty issues. 
* Remove MethodCategory and use annotations instead. Add a new annotation 
ReadOnly.
* Idea of SyncInfo is also to add more fields in the future. 
NamenodeProtocol#getTransactionID is commented as NameNodeProtocol rather that 
ClientProtocol, so I add getSyncInfo() for ClientProtocol. Remove state from 
SyncInfo because we no longer need it. 

> Add a Client API and Proxy Provider to enable stale read from Standby
> ---------------------------------------------------------------------
>
>                 Key: HDFS-10702
>                 URL: https://issues.apache.org/jira/browse/HDFS-10702
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Jiayi Zhou
>            Assignee: Jiayi Zhou
>            Priority: Minor
>         Attachments: HDFS-10702.001.patch, HDFS-10702.002.patch, 
> HDFS-10702.003.patch, HDFS-10702.004.patch, StaleReadfromStandbyNN.pdf
>
>
> Currently, clients must always talk to the active NameNode when performing 
> any metadata operation, which means active NameNode could be a bottleneck for 
> scalability. One way to solve this problem is to send read-only operations to 
> Standby NameNode. The disadvantage is that it might be a stale read. 
> Here, I'm thinking of adding a Client API to enable/disable stale read from 
> Standby which gives Client the power to set the staleness restriction.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to