devsnack/control-repo
1
0
Fork 0
Code Releases Activity
acf1cf7ffd
control-repo/site/profile/manifests/pe_postgresql_management.pp

44 lines
1.5 KiB
ObjectPascal
Raw Normal View History

Add autovacuum settings to pe-postgresql In the past I've seen the console and puppetdb databases grow much larger than expected and I have a hypothesis that this is because the default 20% setting for autovacuum is too high for our workload. So, there's a potential that changing this to 1% might be too low and might reduce performance but it should reduce disk usage and it can always be tuned upward if the performance hit is too large, however, it is much more difficult to reduce the size of a database after it has grown too large. Basically, I'm erroring on the side of using less disk space and hopefully less outages due to running out of disk space and we can open a conversation on performance later if one needs to be had.
2015-12-29 22:30:58 +00:00
class profile::pe_postgresql_management (
Add data type validation to pe_postgresql_management profile Prior to this commit 3 of the 4 parameters were not validated. After this commit, the parameters are correctly validated. Due to MODULES-2960 $autovacuum_scale_factor is validated as a float but then is converted to a string to pass it to the value attribute of postgresql_conf.
2016-01-11 17:47:16 +00:00
Float[0,1] $autovacuum_scale_factor = 0.01,
Boolean $manage_postgresql_service = true,
Boolean $all_in_one_pe_install = true,
Boolean $include_pe_databases_maintenance = true,
Add autovacuum settings to pe-postgresql In the past I've seen the console and puppetdb databases grow much larger than expected and I have a hypothesis that this is because the default 20% setting for autovacuum is too high for our workload. So, there's a potential that changing this to 1% might be too low and might reduce performance but it should reduce disk usage and it can always be tuned upward if the performance hit is too large, however, it is much more difficult to reduce the size of a database after it has grown too large. Basically, I'm erroring on the side of using less disk space and hopefully less outages due to running out of disk space and we can open a conversation on performance later if one needs to be had.
2015-12-29 22:30:58 +00:00
) {
$postgresql_service_resource_name = 'postgresqld'
$postgresql_service_name = 'pe-postgresql'
$notify_postgresql_service = $manage_postgresql_service ? {
true => Service[$postgresql_service_resource_name],
default => undef,
}
Notify console-services when restarting postgresql Due to an issue where console-services fails to complete about 2 requests after a restart of postgresql, let's go ahead and restart the console-services service if we restart the postgresql service. If the console-services is not on the same node as postgresql then set all_in_one_pe_install to false and console-services will not be restarted.
2015-12-29 22:30:58 +00:00
$notify_console_services = $all_in_one_pe_install ? {
true => Service['pe-console-services'],
default => undef,
}
Add autovacuum settings to pe-postgresql In the past I've seen the console and puppetdb databases grow much larger than expected and I have a hypothesis that this is because the default 20% setting for autovacuum is too high for our workload. So, there's a potential that changing this to 1% might be too low and might reduce performance but it should reduce disk usage and it can always be tuned upward if the performance hit is too large, however, it is much more difficult to reduce the size of a database after it has grown too large. Basically, I'm erroring on the side of using less disk space and hopefully less outages due to running out of disk space and we can open a conversation on performance later if one needs to be had.
2015-12-29 22:30:58 +00:00
if $manage_postgresql_service {
service { $postgresql_service_resource_name :
name => $postgresql_service_name,
ensure => running,
enable => true,
Notify console-services when restarting postgresql Due to an issue where console-services fails to complete about 2 requests after a restart of postgresql, let's go ahead and restart the console-services service if we restart the postgresql service. If the console-services is not on the same node as postgresql then set all_in_one_pe_install to false and console-services will not be restarted.
2015-12-29 22:30:58 +00:00
notify => $notify_console_services
Add autovacuum settings to pe-postgresql In the past I've seen the console and puppetdb databases grow much larger than expected and I have a hypothesis that this is because the default 20% setting for autovacuum is too high for our workload. So, there's a potential that changing this to 1% might be too low and might reduce performance but it should reduce disk usage and it can always be tuned upward if the performance hit is too large, however, it is much more difficult to reduce the size of a database after it has grown too large. Basically, I'm erroring on the side of using less disk space and hopefully less outages due to running out of disk space and we can open a conversation on performance later if one needs to be had.
2015-12-29 22:30:58 +00:00
}
}
Add data type validation to pe_postgresql_management profile Prior to this commit 3 of the 4 parameters were not validated. After this commit, the parameters are correctly validated. Due to MODULES-2960 $autovacuum_scale_factor is validated as a float but then is converted to a string to pass it to the value attribute of postgresql_conf.
2016-01-11 17:47:16 +00:00
#The value attribute of postgresql_conf requires a string despite validating a float above
#https://tickets.puppetlabs.com/browse/MODULES-2960
Add autovacuum settings to pe-postgresql In the past I've seen the console and puppetdb databases grow much larger than expected and I have a hypothesis that this is because the default 20% setting for autovacuum is too high for our workload. So, there's a potential that changing this to 1% might be too low and might reduce performance but it should reduce disk usage and it can always be tuned upward if the performance hit is too large, however, it is much more difficult to reduce the size of a database after it has grown too large. Basically, I'm erroring on the side of using less disk space and hopefully less outages due to running out of disk space and we can open a conversation on performance later if one needs to be had.
2015-12-29 22:30:58 +00:00
#http://www.postgresql.org/docs/9.4/static/runtime-config-autovacuum.html
postgresql_conf { ['autovacuum_vacuum_scale_factor', 'autovacuum_analyze_scale_factor'] :
ensure => present,
target => '/opt/puppetlabs/server/data/postgresql/9.4/data/postgresql.conf',
Add data type validation to pe_postgresql_management profile Prior to this commit 3 of the 4 parameters were not validated. After this commit, the parameters are correctly validated. Due to MODULES-2960 $autovacuum_scale_factor is validated as a float but then is converted to a string to pass it to the value attribute of postgresql_conf.
2016-01-11 17:47:16 +00:00
value => "${autovacuum_scale_factor}",
Add autovacuum settings to pe-postgresql In the past I've seen the console and puppetdb databases grow much larger than expected and I have a hypothesis that this is because the default 20% setting for autovacuum is too high for our workload. So, there's a potential that changing this to 1% might be too low and might reduce performance but it should reduce disk usage and it can always be tuned upward if the performance hit is too large, however, it is much more difficult to reduce the size of a database after it has grown too large. Basically, I'm erroring on the side of using less disk space and hopefully less outages due to running out of disk space and we can open a conversation on performance later if one needs to be had.
2015-12-29 22:30:58 +00:00
notify => $notify_postgresql_service,
}
Add pe_databases::maintenance to Puppetfile and profile Default to inlcuding a cron job for running vacuumdb --analyze and reindxdx for all databases.
2016-01-11 17:40:46 +00:00
#https://github.com/npwalker/pe_databases
if $include_pe_databases_maintenance {
include pe_databases::maintenance
}
Add autovacuum settings to pe-postgresql In the past I've seen the console and puppetdb databases grow much larger than expected and I have a hypothesis that this is because the default 20% setting for autovacuum is too high for our workload. So, there's a potential that changing this to 1% might be too low and might reduce performance but it should reduce disk usage and it can always be tuned upward if the performance hit is too large, however, it is much more difficult to reduce the size of a database after it has grown too large. Basically, I'm erroring on the side of using less disk space and hopefully less outages due to running out of disk space and we can open a conversation on performance later if one needs to be had.
2015-12-29 22:30:58 +00:00
}
Copy Permalink