Overlord save segment metadata duplicate entry expection

the expetion bellow makes my overlord respone the rest request with a large delay. i find a issue similar with it (https://github.com/druid-io/druid/issues/2793) which was fixed in 0.9.0,my version is 0.9.2.

362FAD1AF22D743AB121F0BC60E6F7AB8430D8’}, finder:}]

2017-04-01 05:45:54,560 at org.skife.jdbi.v2.SQLStatement.internalExecute(SQLStatement.java:1334) ~[jdbi-2.63.1.jar:2.63.1]

2017-04-01 05:45:54,560 at org.skife.jdbi.v2.Update.execute(Update.java:56) ~[jdbi-2.63.1.jar:2.63.1]

2017-04-01 05:45:54,560 at io.druid.metadata.IndexerSQLMetadataStorageCoordinator$3.inTransaction(IndexerSQLMetadataStorageCoordinator.java:571) ~[druid-server-0.9.2.1-SNAPSHOT.jar:0.9.2]

2017-04-01 05:45:54,560 at io.druid.metadata.IndexerSQLMetadataStorageCoordinator$3.inTransaction(IndexerSQLMetadataStorageCoordinator.java:392) ~[druid-server-0.9.2.1-SNAPSHOT.jar:0.9.2]

2017-04-01 05:45:54,560 at org.skife.jdbi.v2.tweak.transactions.LocalTransactionHandler.inTransaction(LocalTransactionHandler.java:184) ~[jdbi-2.63.1.jar:2.63.1]

2017-04-01 05:45:54,560 at org.skife.jdbi.v2.BasicHandle.inTransaction(BasicHandle.java:327) ~[jdbi-2.63.1.jar:2.63.1]

2017-04-01 05:45:54,560 at org.skife.jdbi.v2.DBI$5.withHandle(DBI.java:333) ~[jdbi-2.63.1.jar:2.63.1]

2017-04-01 05:45:54,560 at org.skife.jdbi.v2.DBI.withHandle(DBI.java:281) ~[jdbi-2.63.1.jar:2.63.1]

2017-04-01 05:45:54,560 … 60 more

2017-04-01 05:45:54,560 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry ‘perflog-min_2017-04-01T05:45:00.000Z_2017-04-01T05:50:00.000Z_20’ for key ‘PRIMARY’

2017-04-01 05:45:54,560 at sun.reflect.GeneratedConstructorAccessor88.newInstance(Unknown Source) ~[?:?]

2017-04-01 05:45:54,560 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_45]

2017-04-01 05:45:54,560 at java.lang.reflect.Constructor.newInstance(Constructor.java:422) ~[?:1.8.0_45]

2017-04-01 05:45:54,560 at com.mysql.jdbc.Util.handleNewInstance(Util.java:404) ~[mysql-connector-java-5.1.38.jar:5.1.38]

2017-04-01 05:45:54,560 at com.mysql.jdbc.Util.getInstance(Util.java:387) ~[mysql-connector-java-5.1.38.jar:5.1.38]

``

anyone who know why this will happen?

thank you .

Found the same exception, did you solve this?

在 2017年4月1日星期六 UTC+8下午2:40:51,guav…@gmail.com写道: