change default refresh delays and drain durations#733
change default refresh delays and drain durations#733
Conversation
|
|
||
| ## Set enableTracing to false to disable request tracing. | ||
| enableTracing: true | ||
| zipkinAddress: zipkin.{ISTIO_NAMESPACE}:9411 |
There was a problem hiding this comment.
These settings won't take effect. Please update to the new API definitions. The parser will ignore any undefined fields.
There was a problem hiding this comment.
?
the SHA in pilot's WORKSPACE is at Sep 10th.
commit = "6838a2bfc42260cf0513552a64a457f1cf39041c", # Sep 10, 2017
remote = "https://github.com/istio/api.git",
)```
| # its internal configuration from Istio Pilot. Lower refresh delay | ||
| # results in higher CPU utilization and potential performance loss in | ||
| # exchange for faster convergence. Tweak this value according to your setup. | ||
| discoveryRefreshDelay: 30s |
|
/lgtm |
|
/lgtm cancel //PR changed after LGTM, removing LGTM. @andraxylia @rshriram |
|
/lgtm cancel |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Assign the PR to them by writing The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:You can indicate your approval by writing |
kyessenov
left a comment
There was a problem hiding this comment.
Looks better (but it'd be better to double check test logs that each settings is being applied)
|
It is not. I thought we sourced the yamls in the tests |
|
This configMap has changed in pilot to use a different structure "default". |
|
Yes and I updated the config map here accordingly.
On Mon, Sep 11, 2017 at 7:02 PM Andra Cismaru ***@***.***> wrote:
This configMap has changed in pilot to use a different structure "default".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#733 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AH0qd81L8x5R9X-0AfIgGSFwjZaIWpTjks5shbwPgaJpZM4PTzIU>
.
--
~shriram
|
|
You need to upgrade the pilot SHA to latest master in the same commit, otherwise istioctl kube-inject will fail the validate. |
andraxylia
left a comment
There was a problem hiding this comment.
You need to run updateVersion.sh for any change in template. Sorry for not noticing earlier.
|
Actually, I will approve since I do not want to block the PR, so you can merge it, but please run updateVersions on it. |
|
Pilot sha is now pointing to master. Ran updateVersion.sh as @andraxylia suggested. Lets see if this passes. |
|
/retest |
install/updateVersion.sh
Outdated
| TEMP_DIR="/tmp" | ||
| GIT_COMMIT=false | ||
|
|
||
| ## Install constants for Pilot. Do not change |
There was a problem hiding this comment.
The changes in this file are not needed, but we can remove them later if the tests pass.
It is enough to have the test infra replace the default values.
There was a problem hiding this comment.
Yep, I realized that.. removed it
|
defaults are not being applied as per the regex in go files.. @yutongz any inputs? |
|
Which one is not applied? @rshriram |
|
Right, so there are two things you need to do:
|
|
will close, you can redo from fresh/green without SHA changes (or resolve conflicts on this PR if you want but carefully) - reopen if you want to reuse |
|
@rshriram: The following tests failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Former-commit-id: 4a2140d8bbade09a6bd85a4112d83f520a41844f
Former-commit-id: 5ad7a1bc16d534f0383445f6ce6603db5726bf90
…istio#733) This reverts commit ef74122.
* Sync installer I was going to wait for the repo merge, but I wanted to fix any failing tests that may pop up to make that merge smoother * fix e2e
Change the default refresh interval, envoy drain duration. The current interval is suitable only for testing (1s). Increasing the default to 30s results in lesser CPU utilization (for Pilot) and better performance.
Release note: