Skip to content
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

jaeger services failed to deploy, if "es.use-aliases" is enabled #434

Closed
jkandasa opened this issue May 23, 2019 · 0 comments · Fixed by #446
Closed

jaeger services failed to deploy, if "es.use-aliases" is enabled #434

jkandasa opened this issue May 23, 2019 · 0 comments · Fixed by #446
Labels
bug Something isn't working Elasticsearch The issues related to Elasticsearch storage

Comments

@jkandasa
Copy link
Member

I enabled rollover support in the CR file, jaeger services are failed to deploy.
jaeger-operator=1.12.0

Error in the jaeger-operator log:

time="2019-05-23T13:51:36Z" level=error msg="failed to apply the changes" error="CronJob.batch \"jaegerqe-ro-es-rollover\" is invalid: spec.jobTemplate.spec.template.spec.containers[0].volumeMounts[0].name: Not found: \"certs\"" execution="2019-05-23 13:51:36.720354103 +0000 UTC" instance=jaegerqe-ro namespace=jkandasa

CR file:

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: jaegerqe-ro
spec:
  ingress:
    security: none
  strategy: production
  collector:
    replicas: 1
    image: jaegertracing/jaeger-collector:1.12
    resources:
      requests:
        cpu: "1"
        memory: "512Mi"
      limits:
        cpu: "1"
        memory: "512Mi"
    options:
      log-level: info
      metrics-backend: prometheus
      collector:
        num-workers: 20
        queue-size: 100000
      es:
        bulk:
          size: 524288
          workers: 3
          flush-interval: 1000ms
        tags-as-fields:
          all: false
  query:
    replicas: 1
    image: jaegertracing/jaeger-query:1.12
    resources:
      requests:
        cpu: "500m"
        memory: "512Mi"
      limits:
        cpu: "500m"
        memory: "512Mi"
    options:
      log-level: info
      metrics-backend: prometheus
      query:
        port: 16686
  agent:
    strategy: sidecar
    image: jaegertracing/jaeger-agent:1.12
    resources:
    options:
      log-level: info
      metrics-backend: prometheus
      processor:
        jaeger-compact:
          server-queue-size: 100000
          workers: 1000
  storage:
    type: elasticsearch
    esIndexCleaner:
      enabled: false
    dependencies:
      enabled: false
    elasticsearch:
      nodeCount: 3
      resources:
    options:
      es:
        use-aliases: true

operator-log: jaeger-operator-78b4c8d5dd-bngtl.log
rollover-create-mapping log: jaegerqe-ro-es-rollover-create-mapping-kcdfx.log

indices in ES cluster:

sh-4.2$ curl --cacert /etc/openshift/elasticsearch/secret/admin-ca --key /etc/openshift/elasticsearch/secret/admin-key --cert /etc/openshift/elasticsearch/secret/admin-cert https://elasticsearch:9200/_cat/indices?v
health status index                 uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   jaeger-span-000001    aTZjh2bORzOTRgn32qT-uw   3   1          0            0       972b           486b
green  open   .searchguard          tMIWfKm3SWe_VwO8Znefug   1   1          5            0     71.8kb         35.9kb
green  open   jaeger-service-000001 Cxwx1xjQRN6oxa67eREDAg   3   1          0            0       972b           486b

image

@jpkrohling jpkrohling added Elasticsearch The issues related to Elasticsearch storage bug Something isn't working labels May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Elasticsearch The issues related to Elasticsearch storage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants