You may have hit memory pressure caising cassandra to resize your cache. You can change the behavior by modifying reduce_cache_capacity_at in cassandra.yaml
See the comments in such for details. On Sep 4, 2013 4:08 PM, "Daning Wang" <dan...@netseer.com> wrote: > We noticed that key cache could not be fully populated, we have set the > key cache size to 1024M. > > key_cache_size_in_mb: 1024 > > But none of nodes showed the cache capacity is 1G, we have recently > upgraded to 1.2.5, could be an issue in that version? > > Token : (invoke with -T/--tokens to see all 256 tokens) > ID : 0fd912fb-3187-462b-8c8a-7d223751b649 > Gossip active : true > Thrift active : true > Load : 73.16 GB > Generation No : 1372374984 > Uptime (seconds) : 5953779 > Heap Memory (MB) : 5440.59 / 10035.25 > Data Center : dc1 > Rack : rac1 > Exceptions : 34601 > Key Cache : size 540060752 (bytes), capacity 540060796 (bytes), > 12860975403 hits, 15535054378 requests, 0.839 recent hit rate, 14400 save > period in seconds > Row Cache : size 0 (bytes), capacity 0 (bytes), 0 hits, 0 requests, > NaN recent hit rate, 0 save period in seconds > > Thanks, > > Daninng >
