mirror of
https://github.com/fnproject/fn.git
synced 2022-10-28 21:29:17 +03:00
6a7973e6b6
the mqs are storing a models.Task, which was not incorporating all the fields that are in a task.Config. I would very much like to merge these two things, but expect to do this in a future restructuring as both are used widely and not cordoned off properly (Config has a channel, stdin, stdout, stderr -- and isn't just a 'config', so to speak, as Task is). Since a task.Config is what is used to actually run a container, the result of the aforementioned deficiency was #193 where tasks are improperly configured and ran (namely, memory wrong). async tasks can still not be hot, they will be reverted to default format. would also like to fix this (also part of restructuring). I actually started doing this, hence the changes to those files (the surface area of the change is small and discourages improper future use, so I've left what I've done). this will: closes #193 closes #195 closes #154 removes many unused fields in models.Task, since we have not implemented retries. priority & delay are left, even though they are not used either, the main goal of this is to resolve #193 and both these fields are strongly plumbed into all the mqs, so punting on those two.
37 lines
1.3 KiB
Markdown
37 lines
1.3 KiB
Markdown
# Message Queues
|
|
|
|
A message queue is used to coordinate asynchronous function calls that run through Oracle Functions.
|
|
|
|
We currently support the following message queues and they are passed in via the `MQ_URL` environment variable. For example:
|
|
|
|
```sh
|
|
docker run -e "MQ_URL=redis://localhost:6379/" ...
|
|
```
|
|
|
|
## [Bolt](https://github.com/boltdb/bolt) (default)
|
|
|
|
URL: `bolt:///fn/data/functions-mq.db`
|
|
|
|
See Bolt in databases above. The Bolt database is locked at the file level, so
|
|
the file cannot be the same as the one used for the Bolt Datastore.
|
|
|
|
## [Redis](http://redis.io/)
|
|
|
|
See Redis in databases above.
|
|
|
|
## [IronMQ](https://www.iron.io/platform/ironmq/)
|
|
|
|
URL: `ironmq://project_id:token@mq-aws-us-east-1.iron.io/queue_prefix`
|
|
|
|
IronMQ is a hosted message queue service provided by [Iron.io](http://iron.io). If you're using Oracle Functions in production and don't
|
|
want to manage a message queue, you should start here.
|
|
|
|
The IronMQ connector uses HTTPS by default. To use HTTP set the scheme to
|
|
`ironmq+http`. You can also use a custom port. An example URL is:
|
|
`ironmq+http://project_id:token@localhost:8090/queue_prefix`.
|
|
|
|
## What about message queue X?
|
|
|
|
We're happy to add more and we love pull requests, so feel free to add one! Copy one of the implementations above as a starting point.
|
|
|