Dashboard not saving - ES "document already exists"

[marcinkubica]

One of the mysterious cases where dashboard layout is not being saved.

However when I selected to save this dashboard with time-date it did save.
And because I didn't want it to have stored time I've saved again, deselected the time-save option and ES did not complain, however dashboard layout is still not saved properly.

I've been mentioning a bug around saving/not saving with time-store already on various occasions xD

I'll see if I can come up with a reproducible case soon.

On the same barrel - why not return ES errors back to kibana?

[2016-03-02 10:30:02,500][INFO ][rest.suppressed          ] /.kibana-tiger/dashboard/{dashboard-name} Params: {index=.kibana-tiger, op_type=create, id={dashboard-name}, type=dashboard}
RemoteTransportException[[{node-name}][10.88.59.141:9300][indices:data/write/index]]; nested: RemoteTransportException[[{node-name}][10.88.59.141:9300][indices:data/write/index[p]]]; nested: DocumentAlreadyExistsException[[dashboard][{dashboard-name}]: document already exists];
Caused by: RemoteTransportException[[{node-name}][10.88.59.141:9300][indices:data/write/index[p]]]; nested: DocumentAlreadyExistsException[[dashboard][{dashboard-name}]: document already exists];
Caused by: [.kibana-tiger][[.kibana-tiger][0]] DocumentAlreadyExistsException[[dashboard][{dashboard-name}]: 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:515)
        at org.elasticsearch.index.engine.Engine$Create.execute(Engine.java:810)
        at org.elasticsearch.action.index.TransportIndexAction.executeIndexRequestOnPrimary(TransportIndexAction.java:236)
        at org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:157)
        at org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:65)
        at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryPhase.doRun(TransportReplicationAction.java:595)
        at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
        at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:263)
        at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:260)
        at org.elasticsearch.transport.TransportService$4.doRun(TransportService.java:350)
        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)

[marcinkubica]

Hi, I think I'm mistaken. You report back on this event (by asking user if he wants to overwrite).

Closing, will come back with reproducible case.