chronos job from mesos/4
Github source:
b8adfbe8
or
master branch
Properties¶
chronos
¶
cassandra
¶
consistency
¶Consistency to use for Cassandra
- Default
ANY
contact_points
¶Comma separated list of contact points for Cassandra
keyspace
¶Keyspace to use for Cassandra
- Default
metrics
port
¶Port for Cassandra
- Default
9042
table
¶Table to use for Cassandra
- Default
chronos
ttl
¶TTL for records written to Cassandra
- Default
3.1536e+07
cassandra_stat_count_table
¶Table to track stat counts in Cassandra
- Default
chronos_stat_count
cluster_name
¶The name of the cluster where Chronos is run
- Default
Chronos Cluster
disable_after_failures
¶Disables a job after this many failures have occurred
- Default
0
enable_checkpoint
¶Enable checkpointing
- Default
true
failover_timeout
¶The failover timeout in seconds for Mesos
- Default
604800
failure_retry
¶Number of ms between retries
- Default
60000
graphite
¶
group_prefix
¶Group prefix for Graphite
host_port
¶Host and port for Graphite
reporting_interval
¶Graphite reporting interval (seconds)
- Default
60
group
¶Group which will own the Chronos services
- Default
vcap
http_credentials
¶Credentials for accessing the Chronos http service (username:password format)
- Default
chronos:chronos
http_port
¶The port Chronos will listen on for HTTP requests
- Default
80
http_realm
¶The security realm associated with the credentials
- Default
mesos
https_port
¶The port Chronos will listen on for HTTPS requests
- Default
443
java_heap_size
¶Java Heap Size for Chronos
- Default
2048m
job_history_limit
¶Number of past job executions to show in history view
- Default
5
leader_max_idle_time
¶The look-ahead time for scheduling tasks in milliseconds
- Default
5000
logrotate
¶
frequency
¶Frequency to run logrotate for Chronos log files (crontab five time and date fields)
- Default
0 * * * *
rotate
¶Number of times Chronos log files are rotated before being removed
- Default
"7"
size
¶Size before Chronos log files are rotated
- Default
10M
from
¶Mail from field
password
¶Mail password (for auth)
server
¶Address of the mailserver
ssl
¶Mail SSL
user
¶Mail user (for auth)
mesos_framework_name
¶The framework name
- Default
Chronos
mesos_role
¶The Mesos role to run tasks under
- Default
'*'
mesos_task_cpu
¶Number of CPUs to request from Mesos for each task
- Default
0.1
mesos_task_disk
¶Amount of disk capacity to request from Mesos for each task (MB)
- Default
256
mesos_task_mem
¶Amount of memory to request from Mesos for each task (MB)
- Default
128
mesos_user
¶The mesos user to run the processes under
- Default
vcap
raven
¶
dsn
¶Raven DSN for connecting to a raven or sentry event service
reconciliation_interval
¶Reconciliation interval in seconds
- Default
600
schedule_horizon
¶The look-ahead time for scheduling tasks in seconds
- Default
60
slack
¶
channel
¶The channel to post to in Slack
token
¶Token needed for posting to Slack
url
¶Webhook URL for posting to Slack
task_epsilon
¶The default epsilon value for tasks in seconds
- Default
60
user
¶User which will own the Chronos services
- Default
root
zk_path
¶Path in ZooKeeper for storing Chronos state
- Default
/chronos
zk_timeout
¶The timeout for ZooKeeper in milliseconds
- Default
10000
mesos
¶
principal
¶Mesos principal
secret
¶Mesos secret
zk_state
¶Path in ZooKeeper for storing Mesos state
- Default
mesos
zookeeper
¶
client_port
¶Port at which the clients will connect to Apache Zookeeper
- Default
2181
servers
¶List of all Apache Zookeeper server host IP/hostnames
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/chronos/
directory
(learn more).
bin/chronos_ctl
(frombin/chronos_ctl.erb
)bin/job_properties.sh
(frombin/job_properties.sh.erb
)config/chronos_logrotate.cron
(fromconfig/chronos_logrotate.cron.erb
)config/logrotate.conf
(fromconfig/logrotate.conf.erb
)config/zoo_hosts.cfg
(fromconfig/zoo_hosts.cfg.erb
)config/zoo_mesos.cfg
(fromconfig/zoo_mesos.cfg.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.