mysql job from cf-mysql/30
Github source:
63cc5347
or
master branch
Properties¶
cf_mysql
¶
mysql
¶
admin_password
¶Password for the MySQL server admin user
admin_username
¶Username for the MySQL server admin user
- Default
root
binlog_enabled
¶Enable binlogs across all nodes
- Default
true
binlog_expire_days
¶Time in days to store binlogs before purging
- Default
60
character_set_server
¶Default character set. Note that while the MariaDB default is latin1, we default to utf8.
- Default
utf8
cluster_health
¶
log_interval
¶Time in seconds between log entries for cluster health
- Default
30
password
¶Password for the cluster logger health user
cluster_ips
¶Optional, list of nodes. Must have the same number of ips as there are nodes in the cluster
collation_server
¶Default collation. Use SHOW COLLATION to view the valid collations for your character set.
- Default
utf8_unicode_ci
database_startup_timeout
¶How long the startup script waits for the database to come online (in seconds)
disable_auto_sst
¶When disable_auto_sst is true, nodes unable to IST will be prevented from automatically deleting their data and performing an SST
- Default
true
galera_healthcheck
¶
db_password
¶Password used by the sidecar to connect to the database
endpoint_password
¶Password used by the sidecar endpoints for Basic Auth
endpoint_username
¶Username used by the sidecar endpoints for Basic Auth
port
¶Port used by sidecar process to listen on
- Default
9200
galera_port
¶Port which Galera Cluster uses for communication across nodes
- Default
4567
gcache_size
¶Cache size used by galera (maximum amount of data possible in an IST), in MB
- Default
512
ib_log_file_size
¶Size of the ib_log_file used by innodb, in MB
- Default
1024
innodb_buffer_pool_instances
¶Optional, number of buffer pool instances for InnoDB used if innodb_buffer_pool_size > 1GB
innodb_buffer_pool_size
¶Optional, the size in bytes of the memory buffer InnoDB uses to cache data and indexes of its tables
innodb_lock_wait_timeout
¶Optional, time in seconds that an InnoDB transaction waits for an InnoDB row lock
log_conflicts
¶Defines whether the node logs additional information about conflicts. The values that were in conflict are logged, so it is possible for user data to end up in the logs.
- Default
true
log_queries_not_using_indexes
¶Queries that don’t use an index, or that perform a full index scan where the index doesn’t limit the number of rows, will be logged to the slow query log.
- Default
false
max_allowed_packet
¶The maximum size in bytes of a packet or a generated/intermediate string
- Default
256M
max_connections
¶Maximum total number of database connections for the node
- Default
1500
max_heap_table_size
¶The maximum size (in rows) to which user-created MEMORY tables are permitted to grow
- Default
1.6777216e+07
max_open_files
¶Configure this number to be comfortably larger than the maximum number of tables you expect the database to support.
- Default
65536
port
¶Port the mysql server should bind to
- Default
3306
previous_admin_username
¶Previous username of the MySQL server admin user to be removed
roadmin_enabled
¶Whether read only user is enabled
- Default
false
roadmin_password
¶Password for the MySQL server read-only admin user
seeded_databases
¶Set of databases to seed
- Default
{}- Example
|+ - name: db1 username: user1 password: pw1 - name: db2 username: user2 password: pw2
server_audit_events
¶Enable audit logging and specify types of events that will be logged. If null, then logging is disabled
- Example
connect,query_ddl,query_dml,query_dcl
server_audit_excluded_users
¶Other database users to exclude from audit logging
- Default
[]- Example
|+ - monitoring_user - other_excluded_user - bot_user
server_audit_file_rotate_size_in_mb
¶Size in MB of each audit log file
- Default
100
server_audit_file_rotations
¶Number of audit file rotations to keep
- Default
30
skip_name_resolve
¶Do not restrict connections to database based on hostname
- Default
true
tmp_table_size
¶The maximum size (in bytes) of internal in-memory temporary tables
- Default
3.3554432e+07
userstat
¶Enables user statistics, adding several new information schema tables and new FLUSH and SHOW commands.
- Default
false
wsrep_debug
¶When set to 1 or 2, the database server logs additional events surrounding errors to help in identifying and correcting problems. Note, these logs are written to disk and to syslog. Enabling this will possibly expose unencrypted application data.
- Default
0
wsrep_max_ws_rows
¶Maximum permitted number of rows per writeset.
- Default
131072
wsrep_max_ws_size
¶Maximum permitted size in bytes per writeset.
- Default
1.073741824e+09
syslog_aggregator
¶
address
¶IP address for syslog aggregator
all
¶Define whether forwarders should also send non-mysql syslog activity to the aggregator.
- Default
false
port
¶TCP port of syslog aggregator
transport
¶Transport to be used when forwarding logs (tcp|udp|relp).
- Default
tcp
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/mysql/
directory
(learn more).
bin/cluster_health_logger_ctl
(fromcluster_health_logger_ctl.erb
)bin/galera-healthcheck_ctl
(fromgalera-healthcheck_ctl.erb
)bin/gra-log-purger.sh
(fromgra-log-purger.sh.erb
)bin/gra-log-purger_ctl
(fromgra-log-purger_ctl.erb
)bin/mariadb_ctl
(frommariadb_ctl.erb
)bin/pre-start
(frompre-start-setup.erb
)bin/pre-start-execution
(frompre-start-execution.erb
)config/cluster_health_logger_config.yml
(fromcluster_health_logger_config.yml.erb
)config/cluster_health_logger_setup.sql
(fromcluster_health_logger_setup.sql.erb
)config/galera_healthcheck_config.yaml
(fromgalera_healthcheck_config.yaml.erb
)config/galera_healthcheck_setup.sql
(fromgalera_healthcheck_setup.sql.erb
)config/mariadb_ctl_config.yml
(frommariadb_ctl_config.yml.erb
)config/mariadb_init
(frommariadb_init.erb
)config/my.cnf
(frommy.cnf.erb
)config/mylogin.cnf
(frommylogin.cnf.erb
)config/mysql_audit_logs.logrotate
(frommysql_audit_logs.logrotate.erb
)config/syslog_forwarder.conf
(fromsyslog_forwarder.conf.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.