Helo,
I have many doubts about the operation and monitoring Cahe-digests.
I do not know how to access the summaries created by the same, as I do?!
I do not know how to ensure that all cache servers are utilising and
swapping the summary cache_digests between them , is need a tag
referencing she?
The cache-digests is only an information exchange protocol between the
caches that have to be used with a architecture of a squid (mesh,
hierarquic, multicast)?
Looking at my scenario, you can point my errors.
RAM
#cache_mem 16 MB
cache_mem 128 MB
maximum_object_size_in_memory 64 KB
# HD
#cache_dir aufs /var/spool/squid 512 16 256
cache_dir aufs /var/spool/squid 512 16 256
#maximum_object_size 128 MB
maximum_object_size 16 MB
minimum_object_size 0 KB
# Cache Threshold limits
cache_swap_low 90
cache_swap_high 100
#log_icp_queries on
# Scenario 4. cache_didests
#cache_peer 192.168.15.200 parent 3128 3130 roun-robin
cache_peer 192.168.15.201 parent 3128 3130 digest-url= 192.168.15.200
192.168.15.202 192.168.15.203
cache_peer 192.168.15.202 parent 3128 3130 digest-url= 192.168.15.200
192.168.15.201 192.168.15.203
cache_peer 192.168.15.203 parent 3128 3130 digest-url= 192.168.15.200
192.168.15201 192.168.15.202
#Tags cache-digest
digest_generation on
digest_bits_per_entry 5
digest_rebuild_period 3600
digest_rewrite_period 3600
digest_rebuild_chunk_percentage 10
digest_swapout_chunk_size 4096 bytes
#icp_port 3130
#prefer_direct off
# Cache Uploads
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern . 0 20% 4320
# Basic configuration
http_port 3128 transparent
visible_hostname mc2-node01
acl cloud src 192.168.15.0/24
#icp_access allow cloud
acl all src 0.0.0.0/0.0.0.0
#icp_access deny all
grateful!
----------------------------------------------------------------------------------
Igor Rafael da Rocha
Received on Wed Jul 20 2011 - 13:48:23 MDT
This archive was generated by hypermail 2.2.0 : Thu Jul 21 2011 - 12:00:07 MDT