Skip to content

Verbose dangling indices logging #17435

@jasontedor

Description

@jasontedor

While investigating #17319, I had started two nodes built from master, and indexed some data. I thought I killed these nodes but one of them was still running. I started another node and it produced the following in its logs:

[2016-03-30 22:51:39,322][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:39,335][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:39,375][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:39,495][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:39,524][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:39,543][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:39,571][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:39,630][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:40,049][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:40,183][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:40,214][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:40,251][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2016-03-30 22:51:40,573][WARN ][gateway                  ] [Ani-Mator] [[i/CetR0D_FTdmYi5IcTE55EA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata

I tried to reproduce this from a fresh cluster, but it did not immediately reproduce. I restored the shared data directory for this cluster from backup and the issue appeared again so there appears to be something special here.

  1. Package the elasticsearch tar from master
  2. Extract the tar into some location /path/to/elasticsearch
  3. Extract the attached data.tar.gz into /path/to/elasticsearch/data
  4. Start Elasticsearch twice from /path/to/elasticsearch/bin/elasticsearch
  5. 💥

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions