-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
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
[Bug]: Cassandra traceTTL is ignored in Jaeger CRD #2589
Labels
bug
Something isn't working
Comments
Hi @stephen-tatari thanks for reporting. |
Looks like this is due to Argo stripping quotes from the YAML string, which causes values like @iblancasa I could, just not too familiar with the Go codebase to contribute something quickly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
As a Jaeger administrator, I want to be able to set a custom TTL on my Cassandra datastore to something greater than the default (2d).
Steps to reproduce
Jaeger
resource like the following:trace_ttl
is still the default172800
seconds (2 days):Expected behavior
I expected the schema job would run with an environment variable
TRACE_TTL
equal to604800
seconds (7 days).Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
1.54.0
SDK
OpenTelemetry Python SDK 0.48 via OpenTelemetry Collector 0.98.0
Pipeline
Python OTEL SDK -> OTEL Collector -> Jaeger Collector -> Cassandra
Stogage backend
Cassandra 4.1.4
Operating system
Linux
Deployment model
Kubernetes 1.27 running on EKS
Deployment configs
No response
The text was updated successfully, but these errors were encountered: