Details
-
New Feature
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- depends upon
-
HDFS-10519 Add a configuration option to enable in-progress edit log tailing
- Resolved
- is related to
-
HDFS-8940 Support for large-scale multi-tenant inotify service
- Open
- relates to
-
HDFS-12943 Consistent Reads from Standby Node
- Resolved