Linkerd Destination pods continuously stop watch and establish watch #6877
-
We don't know if this is normal behaviour, but our logs are filled by the Linkerd Destination pods:
These are the logs for a single service, but we have 50+ services so our logs are just filled with these 'Stopping watch' and 'Establishing watch' log messages. Should we just change the log level to warn? What causes the destination pod to stop / establish these watches? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
This is normal expected behavior because watches will start and stop as necessary depending on traffic patterns. I agree that these logs are a little bit noisy. We could consider changing these log messages to DEBUG level. Please feel free to file a Linkerd issue or Pull Request if you are interested. |
Beta Was this translation helpful? Give feedback.
This is normal expected behavior because watches will start and stop as necessary depending on traffic patterns. I agree that these logs are a little bit noisy. We could consider changing these log messages to DEBUG level. Please feel free to file a Linkerd issue or Pull Request if you are interested.