Issues with hardcoded 2s DNS timeout

[Amit-PivotalLabs]

Hi all,

Several of our users have experienced issues with the hard-coded 2s DNS timeout in how Consul serves DNS. Some of this has to do with how we operate Consul, some has to do with Consul itself. For plenty of context, you can take a look at this thread.

Would you folks be interested in a PR along these lines? If so, how would this fit into Consul's release cadence, i.e. what's the time scale to go from PR to patch release?

Thanks,
Amit

/cc @Pivotal-Pierre-Delagrave @zankich @keymon

[slackpad]

Hi @Amit-PivotalLabs something like this seems pretty reasonable. Consul 0.7 should ship shortly and I'm trying to avoid new stuff at this point, but this should be able to make it into a point release following that one.

[Amit-PivotalLabs]

Thanks! We'll probably submit a PR soon.

On Wed, Aug 31, 2016 at 11:57 PM, James Phillips notifications@github.com
wrote:

Hi @Amit-PivotalLabs https://github.com/Amit-PivotalLabs something like
this seems pretty reasonable. Consul 0.7 should ship shortly and I'm trying
to avoid new stuff at this point, but this should be able to make it into a
point release following that one.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#2309 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC9t3pVLQFWbSyWiEwH4_bcOrA6kzVYbks5qlndPgaJpZM4JunLu
.