{"task": {"agent_timeout": 3000, "task": "codegen__jaegertracing__jaeger-7132", "verifier_timeout": 3000, "instruction": "This is a code generation task. You are expected to write working code that solves the described problem.\n<issue>\n      Discussed in https://github.com/orgs/jaegertracing/discussions/7105\n\n<sup>Originally posted by **aujjwal-smarsh** May  8, 2025</sup>\nHello folks,\n\nI am working on deploying Jaeger V2 with OpenTelemetry CRD. The storage backend is Elasticsearch. I have deployed it in my local cluster, and it is working fine. Though I am struggling with one issue. I want to tune the queue size and retry mechanism for exporter failures.\n\nI found that we can set the queue size using \n\n```\n jaeger_storage_exporter:\n        trace_storage: some_storage\n        queue:\n          enabled: true\n          num_consumers: 10\n          queue_size: 1000\n```\n\nNow, the general [exporterhelper](https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/exporterhelper/README.md#:~:text=can%20be%20modified%3A-,retry_on_failure,-enabled%20(default%20%3D%20true) provides a mechanism to `retry_on_failure`\n```\nretry_on_failure:\n            enabled: true\n            initial_interval: 5s\n            max_interval: 1m\n            max_elapsed_time: 1h\n```\n\nBut I am not able to find any documentation on Jaeger that shows how to leverage the same in the Jaeger v2 storage backend. \n\nAppreciate your help, and thanks in advance.\n\n</issue>\nFocus on implementing the required functionality correctly and efficiently. Treat this as a programming challenge.\nYou are not allowed to read git history.\n", "memory": "8192m", "runnable": false, "difficulty": "hard", "language": "", "cpus": "", "instruction_truncated": false, "category": "code-generation", "compose": false, "has_solution": true, "oracle": null, "docker_image": "", "taskset": "devopsgym", "tags": ["code-generation", "devops-bench"]}, "runs": []}