This message was deleted.

The index_parallel task has a log that looks good, it ends with:

2023-01-06T00:57:39,784 INFO [task-runner-0-priority-0] org.apache.druid.indexing.common.task.batch.parallel.ParallelIndexSupervisorTask - Published [4] segments

2023-01-06T005739,803 INFO [task-runner-0-priority-0] org.apache.druid.indexing.worker.executor.ExecutorLifecycle - Task completed with status: { "id" : "index_parallel_longterm_dmaacdcd_2023-01-06T002742.588Z", "status" : "SUCCESS", "duration" : 1791222, "errorMsg" : null, "location" : { "host" : null, "port" : -1, "tlsPort" : -1 } } 2023-01-06T005739,807 INFO [main] org.apache.druid.java.util.common.lifecycle.Lifecycle - Stopping lifecycle [module] stage [ANNOUNCEMENTS] 2023-01-06T005739,810 INFO [main] org.apache.druid.java.util.common.lifecycle.Lifecycle - Stopping lifecycle [module] stage [SERVER]

Could you please search the coordinator logs for occurrences of this datasource's name? Also, did you previously change the retention rules for this datasource?

it's a new datasource

Any results for

select * from sys.segments where datasource = <new datasource>

?

NO Data

what am I looking for in the logs ?

Any occurrence with the name of the datasource

yes there's the whole indexation process logged

The coordinator loads segment metadata from the metadata store. Could you please try these sql queries on your metadata store (derby / mysql etc)?

select count(*) from druid_pendingSegments where datasource = <new datasource>

select count(*) from druid_segments where datasource = <new datasource>

select count(*) from druid_pendingSegments where datasource = 'longterm';

count ------- 0

any pre-existing rules for the datasource which may be causing it to be not loaded?

select * from druid_rules where dataSource = 'longterm';

The default rule was dropforever, however I changed that thsi morning and created a rule for the datasource, it doesn't look like it helped