I upgraded to v2.4 boost with our cacti server and had Boost on Demand Updating enabled, along with imaging cache. (it has since been disabled). I noticed that everything looked green in the cacti poller...
I would see successful BOOST stats and the poller log would look like:
Code: Select all
10/20/2009 11:05:20 PM - SYSTEM STATS: Time:18.5322 Method:spine Processes:5 Threads:10 Hosts:97 HostsPerProcess:20 DataSources:5524 RRDsProcessed:0
I have attached the boost status data as well:
Code: Select all
Current Boost Status
Boost On Demand Updating: Disabled
Total Data Sources: 5524
Boost Storage Statistics
Database Engine: MyISAM
Current Boost Table Size: 5 MBytes
Avg Bytes/Record: N/A
Max Record Length: Bytes
Max Allowed Boost Table Size: Unlimited
Estimated Maximum Records: Unlimited Records
Previous Runtime
Last Start Time: 2009-10-20 21:43:24
Last Run Duration: 19.0322 Seconds
RRD Updates: 71160
Peak Poller Memory: 57.22 MBytes
Max Poller Memory Allowed: 1024 MBytes
Run Time Configuration
Update Frequency: N/A
Next Start Time: 2009-10-20 22:13:24
Maximum Records: 100000 Records
Maximum Allowed Runtime: 20 Minutes
Boost Server Details
Server Config Status: Disabled
Multiprocess Server: Single Process
Update Timeout: 2 Seconds
Server/Port: localhost@9050
Authorized Update Web Servers: 127.0.0.1
RRDtool Binary Used: /usr/bin/rrdtool
Image Caching
Image Cacing Status: Disabled
Cache Directory: /var/www/html/plugins/boost/cache/
Cached Files: 280 Files
Cached Files Size: 10 MBytes
Code: Select all
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
skip-innodb
skip-locking
skip-external-locking
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
max_connections=300
max_heap_table_size = 3G
key_buffer = 1024M
myisam_sort_buffer_size = 64M
join_buffer_size = 1M
read_buffer_size = 1M
sort_buffer_size = 16M
tmp_table_size = 64M
table_cache = 1024
read_rnd_buffer_size = 2M
thread_concurrency = 8
thread_cache = 200
thread_cache_size = 256
wait_timeout = 180
connect_timeout = 10
max_allowed_packet = 16M
max_connect_errors = 10
# To allow mysqld to connect to a MySQL Cluster management daemon, uncomment
# these lines and adjust the connectstring as needed.
#ndbcluster
#ndb-connectstring="nodeid=4;host=localhost:1186"
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[ndbd]
# If you are running a MySQL Cluster storage daemon (ndbd) on this machine,
# adjust its connection to the management daemon here.
# Note: ndbd init script requires this to include nodeid!
connect-string="nodeid=2;host=localhost:1186"
[ndb_mgm]
# connection string for MySQL Cluster management tool
connect-string="host=localhost:1186"
[mysqldump]
quick
max_allowed_packet = 16M
[myisamchk]
key_buffer = 64M
sort_buffer = 64M
read_buffer = 16M
write_buffer = 16M
I definitely notice that there is severe I/O issues with just the poller (spine) w/o boost. Once I enabled boost everything was MUCH faster, its just that the graphs werent being displayed properly on the hourly/monthly/yearly (the normal graph layout when you click on a host)
Has anyone experienced this issue, or have any ways that would fix it?
I'm using CactiEZ (0.8.7c)on a 64bit machine, and manually upgraded to Boost 2.4.
Any suggestions would be greatly appreciated!!!