upstream: trigger original dst clean only when hosts are there#6152
upstream: trigger original dst clean only when hosts are there#6152mattklein123 merged 4 commits intoenvoyproxy:masterfrom
Conversation
Signed-off-by: Rama Chavali <[email protected]>
|
@venilnoronha That was my original thought - but then looking at the log lines in the loop, if we drop this to trace and leave other two log lines in debug they seem to come out of context. But I agree we will loose the information that it is running - Are you OK, making all three log lines to trace? I am OK changing it like that. |
Signed-off-by: Rama Chavali <[email protected]>
|
@venilnoronha I went ahead and changed all three log lines to trace. LMK, if you think there is a better alternative. |
|
Can we keep your previous logic (and the 3 |
|
I see. I can do that. |
Signed-off-by: Rama Chavali <[email protected]>
| } else { | ||
| ENVOY_LOG(debug, "Removing stale host {}.", host->address()->asString()); | ||
| to_be_removed.emplace_back(host); | ||
| ENVOY_LOG(trace, "stale original dst hosts cleanup triggered"); |
There was a problem hiding this comment.
nit: s/stale/Stale
nit: s/triggered/triggered.
Signed-off-by: Rama Chavali <[email protected]>
|
/retest |
|
🔨 rebuilding |
|
@snowp could you help on reviewing this? |
…proxy#6152) Signed-off-by: Rama Chavali <[email protected]> Signed-off-by: Fred Douglas <[email protected]>
Description: The log line
Cleaning up stale original dst hostsis triggering quite often when upstream log is enabled even there are no hosts. My intention was to control this log line, but I think it does not harm to guard whole cleanup logic with this condition.Risk Level: Low
Testing: Low
Docs Changes: N/A
Release Notes: N/A