Skip to content

proxy job from pxc/0.12.0

Github source: bb5a7df or master branch

Properties

api_aggregator_port

Port for the proxy aggregator API to listen on

Default
8082

api_force_https

Redirect all HTTP requests to the API to HTTPS

Default
true

api_password

Password for Basic Auth used to secure API

api_port

Port for the proxy API to listen on

Default
8080

api_uri

Optional, Base URI registered to the proxies. Used by the proxy aggregator.

Example
proxy-cf-mysql.my-system-domain.com

api_username

Username for Basic Auth used to secure API

Default
proxy

health_port

Port for checking the health of the proxy process

Default
1936

healthcheck_timeout_millis

Timeout (milliseconds) before assuming a backend is unhealthy

Default
5000

inactive_mysql_port

If configured, listens on this port and routes traffic to an inactive mysql node. Useful for queries you do not want to impact other clients

max_open_files

Configure this number to be twice as large as mysql.max_connections

Default
3000

port

Port for the proxy to listen on

Default
3306

shutdown_delay

If using a load balancer above the proxies, enter your load balancer’s unhealthy total threshold time here in seconds. E.g., if your LB polls every 30 seconds, and immediately fails over upon failure, then set this property to 30 seconds.

Default
0

startup_delay

If using a load balancer above the proxies, enter your load balancer’s healthy total threshold time here in seconds. E.g., if your LB polls every 30 seconds and requires 3 successful attempts, then set this property to 90 seconds.

Default
0

type

Used by consumers of the database link to configure database properties

Default
mysql

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/proxy/ directory (learn more).

  • bin/post-start (from post-start.erb)
  • bin/proxy-ctl (from proxy-ctl.erb)
  • config/proxy.yml (from proxy.yml.erb)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.