HPCC-14499 Allow WsECL VIP DNS cache timeout to be configurable #9104
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The DNS cache timeout interval will now be configurable for WsECL VIPS. You can set it to 0 to mean resolve the DNS everytime, -1 to mean keep cached indefinitely, or the number of seconds to keep the DNS resolution cached.
From environment.xml, see dnsInterval attribute:
<EspService build="_" buildSet="ws_ecl" description="WS ECL Service" name="myws_ecl" roxieTimeout="300" workunitTimeout="600"> <ProcessCluster name="ProcessCluster" roxie="myroxie" sendTargetToRoxie="true" dnsInterval="77"
vip="localhost"/>`
Signed-off-by: Anthony Fishbeck anthony.fishbeck@lexisnexis.com