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

Enabling migration.enabled: true in metricbeat.yml breaks the writing of metricbeat index template to elasticsearch #11271

Closed
bhavyarm opened this issue Mar 15, 2019 · 1 comment
Labels

Comments

@bhavyarm
Copy link

bhavyarm commented Mar 15, 2019

  • Version: 7.0.0 BC1 metricbeat/elasticsearch/kibana
  • Operating System: darwin_x86_64
  • Steps to Reproduce:
    If user enables migration.enabled: true in metricbeat.yml - metricbeat cannot write the indexpattern template [metricbeat-7.0.0-rc1] into elasticsearch.

This is what the ES logs say:

2019-03-15T15:10:08,796][INFO ][o.e.x.i.a.TransportPutLifecycleAction] [bhavyarajumandya] updating index lifecycle policy [metricbeat-7.0.0-rc1]
[2019-03-15T15:10:09,025][DEBUG][o.e.a.a.i.t.p.TransportPutIndexTemplateAction] [bhavyarajumandya] failed to put template [metricbeat-7.0.0-rc1]
java.lang.IllegalArgumentException: Invalid [path] value [rabbitmq.node.name] for field alias [rabbitmq.node.name]: an alias cannot refer to itself.
    at org.elasticsearch.index.mapper.FieldTypeLookup.validateAlias(FieldTypeLookup.java:128) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.index.mapper.FieldTypeLookup.copyAndAddAll(FieldTypeLookup.java:83) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.index.mapper.MapperService.internalMerge(MapperService.java:480) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.index.mapper.MapperService.internalMerge(MapperService.java:398) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:323) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.cluster.metadata.MetaDataIndexTemplateService.validateAndAddTemplate(MetaDataIndexTemplateService.java:253) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.cluster.metadata.MetaDataIndexTemplateService.access$300(MetaDataIndexTemplateService.java:65) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.cluster.metadata.MetaDataIndexTemplateService$2.execute(MetaDataIndexTemplateService.java:176) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:47) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:687) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:310) ~[elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:210) [elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:142) [elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150) [elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188) [elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:681) [elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:252) [elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:215) [elasticsearch-7.0.0-rc1.jar:7.0.0-rc1]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
    at java.lang.Thread.run(Thread.java:834) [?:?]
@bhavyarm bhavyarm added bug Metricbeat Metricbeat labels Mar 15, 2019
ruflin added a commit to ruflin/beats that referenced this issue Mar 18, 2019
* rabbitmq.node.name was duplicated and alias pointed to itself
* rabbitmq.connection.name was falsely migrated to `rabbitmq.name`

Also adding tests to Filebeat and Metricbeat to ensure this does not happen again in the future.

Closes elastic#11271
@ruflin
Copy link
Member

ruflin commented Mar 18, 2019

Opened #11284 with a fix and added tests to make sure this does not happen again.

ruflin added a commit that referenced this issue Mar 18, 2019
* rabbitmq.node.name was duplicated and alias pointed to itself
* rabbitmq.connection.name was falsely migrated to `rabbitmq.name`

Also adding tests to Filebeat and Metricbeat to ensure this does not happen again in the future.

Closes #11271
ruflin added a commit to ruflin/beats that referenced this issue Mar 18, 2019
* rabbitmq.node.name was duplicated and alias pointed to itself
* rabbitmq.connection.name was falsely migrated to `rabbitmq.name`

Also adding tests to Filebeat and Metricbeat to ensure this does not happen again in the future.

Closes elastic#11271

(cherry picked from commit feaef40)
ruflin added a commit that referenced this issue Mar 18, 2019
* rabbitmq.node.name was duplicated and alias pointed to itself
* rabbitmq.connection.name was falsely migrated to `rabbitmq.name`

Also adding tests to Filebeat and Metricbeat to ensure this does not happen again in the future.

Closes #11271

(cherry picked from commit feaef40)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants