Package: ganglia-monitor
Version: 3.1.7-2+b1

>From the gmetad.conf:

# In earlier versions of gmetad, hostnames were handled in a case
# sensitive manner
# If your hostname directories have been renamed to lower case,
# set this option to 0 to disable backward compatibility.
# From version 3.2, backwards compatibility will be disabled by default.
# default: 1   (for gmetad < 3.2)
# default: 0   (for gmetad >= 3.2)
case_sensitive_hostnames 1


For new installs, it should be 0

For installs where an existing gmetad.conf is present:
- it should not be changed by the script
- the script should check if the setting is 0 or 1 (or unspecified)
- the script should check if any directories exist with uppercase hostnames
- if the user will be impacted ((because they have uppercase directory
names) && (they have not added the option to gmetad.conf)), the user
should be warned that default behavior is changing and the install
should abort
- the user should be advised to rename directories manually (there is a
script in the distribution for renaming their RRD directories to
lowercase) and then modify their config
- (optional) the script could offer the quick-and-dirty solution:
manually adding (case_sensitive_hostnames 1), but warning the user not
to do so because future versions of Ganglia may have features the depend
on standardized directory naming

Impact of not addressing this config option:
- user could lose historic data or require un-necessary extra effort to
merge historic data with new data
- on restart, gmetad will try to recreate all RRDs immediately using
lowercase directory names - if they have many RRDs and/or long retention
periods (large RRD file sizes), this places a huge IO load on the server
and delays the collection of metric data

Remediation of directory names should not be automated because the user
may have other local scripts that access the directories and need
remediation before they do an upgrade




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to