Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.1.0-beta, 3.0.0-alpha1
-
None
-
Reviewed
Description
As noted in discussion on HADOOP-9688, we can optimize generation of call ID in the RPC client code. Currently, it synchronizes on the Client instance to coordinate access to a shared int. We can switch this to AtomicInteger to avoid lock contention.
Attachments
Attachments
Issue Links
- is part of
-
HDFS-4942 Add retry cache support in Namenode
- Closed
- relates to
-
HADOOP-9688 Add globally unique Client ID to RPC requests
- Closed