baaaaast commented on issue #12288: URL: https://github.com/apache/druid/issues/12288#issuecomment-1256009451
hey @gitmstoute, I had exactly the same problem with the same version. To unblock the situation, I deleted an old database entry in druid_pendingsegments table that should not have remained: druid_db=# select * from druid_pendingsegments; -[ RECORD 1 ]- id | xxx_2022-07-26T00:00:00.000Z_2022-07-26T01:00:00.000Z_2022-08-03T04:44:16.814Z_2427 datasource | xxx created_date | 2022-09-14T09:27:55.647Z start | 2022-07-26T00:00:00.000Z end | 2022-07-26T01:00:00.000Z sequence_name | index_kafka_xxx_44c72010954e750_0 sequence_prev_id | sequence_name_prev_id_sha1 | E6Exxx payload | \xxxx druid_db=# delete from druid_pendingsegments where id='xxx_2022-07-26T00:00:00.000Z_2022-07-26T01:00:00.000Z_2022-08-03T04:44:16.814Z_2427'; -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
