We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We are seeing hundreds of thousands of logs Failed to parse TTL for prepared query , ignoring after upgrading Consul.
Failed to parse TTL for prepared query , ignoring
This was caused by a typo in #20563 that didn't put that warn in an else block. That warning should also include the error message, right?
else
Use prepared queries and v1.19.0
N/A but running v1.19.0
N/A
2024-06-26T23:59:58.950Z [WARN] agent.catalog-data-fetcher: Failed to parse TTL for prepared query , ignoring: ttl=1s prepared_query=publisher-api
The text was updated successfully, but these errors were encountered:
DanStough
Successfully merging a pull request may close this issue.
Overview of the Issue
We are seeing hundreds of thousands of logs
Failed to parse TTL for prepared query , ignoring
after upgrading Consul.This was caused by a typo in #20563 that didn't put that warn in an
else
block. That warning should also include the error message, right?Reproduction Steps
Use prepared queries and v1.19.0
Consul info for both Client and Server
N/A but running v1.19.0
Operating system and Environment details
N/A
Log Fragments
The text was updated successfully, but these errors were encountered: