From 0fb908178ddbc7c9583ac8c7226244b2b66e6d4f Mon Sep 17 00:00:00 2001 From: Jason Tedor Date: Wed, 7 Oct 2015 10:36:05 -0400 Subject: [PATCH] Clarify Javadoc comment regarding CacheSegment locks --- core/src/main/java/org/elasticsearch/common/cache/Cache.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/src/main/java/org/elasticsearch/common/cache/Cache.java b/core/src/main/java/org/elasticsearch/common/cache/Cache.java index 7d811b17813..a8bb4e7b641 100644 --- a/core/src/main/java/org/elasticsearch/common/cache/Cache.java +++ b/core/src/main/java/org/elasticsearch/common/cache/Cache.java @@ -40,7 +40,7 @@ import java.util.function.ToLongBiFunction; * evictions are exposed. *

* The design of the cache is relatively simple. The cache is segmented into 256 segments which are backed by HashMaps. - * The segments are protected by a re-entrant read/write lock. The read/write locks permit multiple concurrent readers + * Each segment is protected by a re-entrant read/write lock. The read/write locks permit multiple concurrent readers * without contention, and the segments gives us write throughput without impacting readers (so readers are blocked only * if they are reading a segment that a writer is writing to). *