You could try changing the `request_timeout_in_seconds` [0 <https://github.com/cloudfoundry-incubator/routing-release/blob/develop/jobs/gorouter/spec#L132-L134>] property in your manifest. However it

Just hasn't been scheduled yet. No known issues at this time. Best Amit

Do you have more than one api_zN instance running? Your logs may be on another VM.

Hi all, The CF Infrastructure team is working on bumping the version of etcd in etcd-release to the latest patch within the version 2 major line [0]. We've run into an issue [1] with the way that etcd

Thanks. I've created a couple stories to address those two requests: https://www.pivotaltracker.com/story/show/129187415 https://www.pivotaltracker.com/story/show/129187421 As it stands, it might be q

I understand. I'm claiming that if consul-release supports just the first two, then you don't really need the third. Can you describe a case where you would want to do the third thing on that list but

Hi Hector, If you are able to configure consul-release to (a) not rewrite /etc/resolv.conf and (b) not listen on port 53, then I assume you would run your own thing like bind or dnsmasq there, and onl

I suspect that if you pushed the app before setting the backend to default to diego, the app's state in the DB still has backend: dea. So CC is trying to schedule it on the DEAs and the first scheduli

Hi all, The .ruby-version file has been removed (see develop branch) and that change will be present in the next final release. Best Amit wrote:

Thanks Hector, Stefan, This all sounds great. Sounds like you just want options to (1) configure which port Consul DNS binds to, and (2) toggle whether or not it makes changes to /etc/resolv.conf, at

Hey all, The CF Release Integration team has extracted a nats-release BOSH release out of cf-release so that it can be independently tested and reused within other deployments. * repo: https://github.

Hey all, The CF Infrastructure team has extracted a postgres-release BOSH release out of cf-release so that it can be independently tested and reused within other deployments. * repo: https://github.c

Hey Neil, The docs say: *Replace CCDB_ENCRYPTION_KEY with a secure key that you generate to encrypt sensitive values in the Cloud Controller database.* I take it to mean, since it doesn't state any co

Hi Richard, This is indeed a recurring problem for which we're trying several processes to address, and it's come up several times on this mailing list as well as in the Foundation's bi-weekly Runtime

Sorry for the delayed response. Thank you for doing this experiment! We have a backlog story to do this and build regression tests to make sure it will always work, and your validation of the proposed

Hi Hector, I'd like to help you, and ensure your CF deployment and internal service discovery in particular works robustly for you in your environment, but I need a lot more clarity on what you're ask

Hi Hector, I'd like to help you, and ensure your CF deployment and internal service discovery in particular works robustly for you in your environment, but I need a lot more clarity on what you're ask

Awesome! wrote:

Consul does allow DNS caching: https://www.consul.io/docs/guides/dns-cache.html. I haven't tried it out. Perhaps it only caches queries that are managed by Consul itself, but queries that would go to

Hi Hector, I believe you offerred [0] to submit a PR to consul-release to deal with the caching and allow stale reads issue [1], we would happily welcome that. I'm less sure about the other suggestion