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

Error: DocumentAlreadyExistsException[[config][4.2.1]: document already exists #5519

Closed
hzbd opened this Issue Nov 29, 2015 · 8 comments

Comments

Projects
None yet
7 participants
@hzbd

hzbd commented Nov 29, 2015

Elasticsearch error log here:

[2015-11-29 14:01:33,155][INFO ][rest.suppressed          ] /.kibana/config/4.2.1 Params: {index=.kibana, op_type=create, id=4.2.1, type=config}
[.kibana][[.kibana][0]] DocumentAlreadyExistsException[[config][4.2.1]: document already exists]
    at org.elasticsearch.index.engine.InternalEngine.innerCreateNoLock(InternalEngine.java:432)
    at org.elasticsearch.index.engine.InternalEngine.innerCreate(InternalEngine.java:390)
    at org.elasticsearch.index.engine.InternalEngine.create(InternalEngine.java:362)
    at org.elasticsearch.index.shard.IndexShard.create(IndexShard.java:531)
    at org.elasticsearch.index.engine.Engine$Create.execute(Engine.java:810)
    at org.elasticsearch.action.support.replication.TransportReplicationAction.executeIndexRequestOnPrimary(TransportReplicationAction.java:1073)
    at org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:170)
    at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryPhase.performOnPrimary(TransportReplicationAction.java:579)
    at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryPhase$1.doRun(TransportReplicationAction.java:452)
    at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

kibana_error

my envs :

es 2.1 & kibana 4.2
centos 6.7 x64
jdk 1.8.0-u66

Any workaround, how can we fix it? appreciate your help. thank you.

@ebuildy

This comment has been minimized.

Show comment
Hide comment
@ebuildy

ebuildy Nov 30, 2015

Contributor

Remove document .kibana/config/4.2.1

curl -XDELETE /.kibana/config/4.2.1
Contributor

ebuildy commented Nov 30, 2015

Remove document .kibana/config/4.2.1

curl -XDELETE /.kibana/config/4.2.1
@rashidkpc

This comment has been minimized.

Show comment
Hide comment
@rashidkpc

rashidkpc Nov 30, 2015

Member

Indeed, remove the existing one

Member

rashidkpc commented Nov 30, 2015

Indeed, remove the existing one

@rashidkpc rashidkpc closed this Nov 30, 2015

@hzbd

This comment has been minimized.

Show comment
Hide comment
@hzbd

hzbd commented Dec 1, 2015

@ebuildy thank you.

@lbjay

This comment has been minimized.

Show comment
Hide comment
@lbjay

lbjay Jan 5, 2016

Pardon me. Just adding a note here in case some future fool (like myself) forgets to revert "index.refresh_interval" from -1 back to the default after a bulk ingest. A fresh kibana install will show this error and no amount of -XDELETE-ing will fix it.

lbjay commented Jan 5, 2016

Pardon me. Just adding a note here in case some future fool (like myself) forgets to revert "index.refresh_interval" from -1 back to the default after a bulk ingest. A fresh kibana install will show this error and no amount of -XDELETE-ing will fix it.

@megastef

This comment has been minimized.

Show comment
Hide comment
@megastef

megastef Jan 17, 2016

Got the same problem with 4.3.1-linux-x64 (refresh interval is 5 seconds)
But if one deletes the Kibana config, all existing configurations are lost. How to deal with it?

megastef commented Jan 17, 2016

Got the same problem with 4.3.1-linux-x64 (refresh interval is 5 seconds)
But if one deletes the Kibana config, all existing configurations are lost. How to deal with it?

@megastef

This comment has been minimized.

Show comment
Hide comment
@megastef

megastef Jan 17, 2016

Do I have to delete the Kibana Index on every Server restart?

megastef commented Jan 17, 2016

Do I have to delete the Kibana Index on every Server restart?

@spalger

This comment has been minimized.

Show comment
Hide comment
@spalger

spalger Jan 18, 2016

Member

@megastef you shouldn't have to clear out the configuration. Does this happen every time you restart? Thats definitely a bug if so. Please open a new ticket describing what is happening.

Member

spalger commented Jan 18, 2016

@megastef you shouldn't have to clear out the configuration. Does this happen every time you restart? Thats definitely a bug if so. Please open a new ticket describing what is happening.

@kjelle

This comment has been minimized.

Show comment
Hide comment
@kjelle

kjelle Jan 28, 2016

Same happens to me. Kibana 4.3.0 on Elasticsearch 2.1.1.
I delete and after a few seconds its back.

kjelle commented Jan 28, 2016

Same happens to me. Kibana 4.3.0 on Elasticsearch 2.1.1.
I delete and after a few seconds its back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment