Matti Paksula
Matti Paksula
What happens when affinity can not be satisfied? 1.3.4 says RuntimeError IIRC
yes, RuntimeError can not be right.
related: #2563
workaround: ``` HostNodeStat.collection.client.command( convertToCapped: HostNodeStat.collection.name, capped: true, size: 10.megabytes ) ```
bump, had to implement a workaround again: https://github.com/matti/terraform-kontena-heroku-master/blob/master/main.tf#L103
Yeah, I think this happened because the master was down? Anyway, isn't the error message a bit misleading?
you need to unbuffer the output: with curl its -N ``` $ curl -N localhost:7379/SUBSCRIBE/testing {"SUBSCRIBE":["subscribe","testing",1]} ``` and then ``` $ curl localhost:7379/PUBLISH/testing/hello {"PUBLISH":1} ``` and subscriber will look like...
6 years later :D
@lamby I know the feeling.
OR better (?) accept a pre made CA from an ENV so that is is the same for every pod running the master regardless of the lifecycle