879a6b4202
do not error if container already exists
2020-08-18 21:15:54 -07:00
0ae8dc1040
scheduler: reduce container churn
...
When we have a lot of app, docker has a tough time keeping up with
the container churn.
The reason why we don't use docker exec is that there is no way
to delete or manage exec containers.
Fixes #732
2020-08-18 20:26:19 -07:00
50dcf827a5
remove console.error use in many places
...
the backtraces just flood the logs
apphealthtask: remove console.error
remove spurious console.dir
cleanup scheduler error logging
2020-06-04 11:21:56 -07:00
2fc3cdc2a2
remove superfluous debug
2020-06-01 09:40:56 -07:00
2e820c343a
remove meaningless debug
2020-05-24 20:11:03 -07:00
efea4ed615
more debug() removal
2020-05-24 11:35:31 -07:00
67a931c4b8
Remove verbose logs
2020-05-24 11:33:53 -07:00
2cdf68379b
Revert "add volume support"
...
This reverts commit b8bb69f730
2020-04-27 22:55:43 -07:00
b8bb69f730
add volume support
...
part of #668 , #569
2020-04-24 22:09:07 -07:00
84cffe8888
Fix debug
2020-01-28 13:51:03 -08:00
dd0fb8292c
Move state enums to the model code
2019-08-30 13:21:51 -07:00
ee9636b496
move use of TEST and CLOUDRON to constants
2019-07-26 10:13:20 -07:00
ff4b09a342
Use the container StartedAt instead of lastDate
...
CronJob.lastDate keeps resetting on every tick. Also, it doesn't
work across box code restarts.
2018-02-27 14:26:40 -08:00
f8c8133148
scheduler: better debugs
2018-02-27 13:54:38 -08:00
938a41e12c
scheduler: give cron jobs a grace period of 30 mins to complete
2018-02-27 13:28:42 -08:00
5d231f4fef
scheduler: do no start all cronjobs at once
2018-02-27 12:44:11 -08:00
b56dcaac68
Only run scheduler when app is healthy
...
Fixes #393
2017-09-03 18:21:13 -07:00
e3c72fa6ce
remove src/ prefix in debug tags
2017-04-23 21:53:59 -07:00
77df520b07
addons is optional in manifest
2017-03-26 21:55:31 -07:00
0384fa9a51
fix debugs
2015-12-23 15:22:36 -08:00
75b19d3883
scheduler: remove scheduler.json
...
don't bother saving state across restarts. needlessly complicated.
2015-12-23 14:27:26 -08:00
c15f84da08
scheduler: do not bother tracking containerIds
2015-12-23 13:29:00 -08:00
8539d4caf1
scheduler: delete containers by name
...
scheduler.json gets nuked during updates. When the box code restarts,
the scheduler is unable to remove old container because the state file
scheduler.json is now gone. It proceeds to create new container but that
does not work because of name conflict.
Fixes #531
2015-12-23 13:23:49 -08:00
5a0f7df377
handle scheduler error
2015-11-22 21:17:17 -08:00
2e54be3df8
Revert "fix crash in scheduler"
...
This reverts commit 3b5e30f922
2015-11-22 21:13:05 -08:00
6625610aca
fix crash in scheduler
2015-11-22 17:22:06 -08:00
3766d67daa
create new container from cloudron exec
2015-11-10 21:36:20 -08:00
88b1cc553f
Use journalctl to get app logs
2015-11-02 14:08:34 -08:00
95b2bea828
Give containers a name
2015-11-02 09:34:31 -08:00
f0047bc1aa
console.error -> debug
2015-10-28 17:05:16 -07:00
16df15cf55
containerId does not mean it is running
2015-10-20 16:56:57 -07:00
3688602d16
test the scheduler
2015-10-20 14:30:50 -07:00
16f025181f
ensure boolean
2015-10-20 12:49:02 -07:00
3808f60e69
appState can be null
2015-10-20 12:32:50 -07:00
db6882e9f5
do not kill containers on restart
2015-10-20 10:22:42 -07:00
3fd9d9622b
schedulerConfig cannot be null
2015-10-20 09:44:46 -07:00
fb2e7cb009
scheduler: crash fixes
2015-10-20 09:36:30 -07:00
852b016389
scheduler: do not save cronjob object in state
...
the cronjob object has lots of js stuff and stringify fails
2015-10-20 01:31:11 -07:00
1f28678c27
scheduler: make it work
2015-10-20 00:05:19 -07:00
ed5d6f73bb
scheduler: fix require
2015-10-19 22:42:13 -07:00
d0360e9e68
scheduler: load/save state
2015-10-19 22:41:42 -07:00
7a840ad15f
scheduler: make stopJobs async
2015-10-19 21:36:55 -07:00
682c2721d2
scheduler: kill existing tasks if they are still running
2015-10-19 21:36:23 -07:00
351d7d22fb
rename tasks to tasksConfig
2015-10-19 16:29:28 -07:00
79999887a9
job -> cronJob
2015-10-19 16:27:03 -07:00
990b7a2d20
implement scheduler
...
- scan for apps every 10 minutes and schedules tasks
- uses docker.exec
- there is no way to control exec container. docker developers
feel exec is for debugging purposes primarily
- future version will be based on docker run instead
part of #519
2015-10-19 14:53:34 -07:00
Girish Ramakrishnan