我目前正在使用 hazelcast 3.9版我嘗試了幾種實現近緩存的方法，但似乎找不到正確的方法。下面我分享了我的代碼，讓我確切地知道我哪里出錯了。    public class NearCacheExample {    public static void main(String[] args) throws IOException     {        HazelcastConfig hzConfig = new HazelcastConfig();        HazelcastInstance hzInstance = hzConfig.getHZInstance();        IMap<Double, String> nearCacheMap = hzInstance.getMap("cacheExample");        for (int i = 0; i < 100000; i++) {            nearCacheMap.set(Math.random(), i + "");        }        long startTime = System.currentTimeMillis();        System.out.println("---------------------------Before Sort----------------------------------");        for (Entry<Double, String> entrySet : nearCacheMap.entrySet()) {            Double key = entrySet.getKey();            String value = entrySet.getValue();        }        long endTime = System.currentTimeMillis();        System.out.println("------------------------------------------------Read Both---------------------------------------------------");        NearCacheStats nearCacheStatistics = nearCacheMap.getLocalMapStats().getNearCacheStats();        System.out.println( "Near Cache hit/miss ratio 3= "                + nearCacheStatistics.getHits());        System.out.println("Near cache implemented or not " + nearCacheMap.getLocalMapStats().getNearCacheStats().getOwnedEntryCount());        System.out.println(" EndTime timeDifference : " + startTime + " " + endTime + " " +(endTime-startTime));    }}Hazelcast 客戶端的配置<near-cache name="default"><in-memory-format>BINARY</in-memory-format><invalidate-on-change>true</invalidate-on-change><eviction eviction-policy="NONE" max-size-policy="ENTRY_COUNT" size="10"/>我還嘗試在 hazelcast-client.xml 文件中更改緩存名稱。似乎沒有任何效果在 hazelcast 服務器端沒有變化。