This message was deleted.
# troubleshootings
Slackbot
06/11/2023, 7:56 PMThis message was deleted.
a
Amatya Avadhanula
06/12/2023, 1:53 AMCould you please check the historical logs corresponding to the stuck load queue?
You could try restarting the coordinator to see if it helps clear the bad segment from the load queue.
(Also, please switch from
curatorhttpv
victor regalado
06/12/2023, 5:07 AM Copy code
Unannouncing segment[<segment>] at path[..]
org.apache.druid.server.coordination.SegmentLoadDropHandler - Completely removing <segment> in [30,000] millis
org.apache.druid.server.SegmentManager - Attempting to close segment <segment>victor regalado
06/12/2023, 5:07 AMonly these 3 log lines
a
Amatya Avadhanula
06/12/2023, 5:09 AMCould you please share the replication factor of your segments and also run the following sys table query from the druid console?
select num_replicas, count(*) from sys.segments group by 1v
victor regalado
06/12/2023, 5:09 AMReplication factor is 2
a
Amatya Avadhanula
06/12/2023, 5:10 AMThe above query should give the count of segments with various replication levels. It's possible that the cluster is overreplicated and segments are being dropped
v
victor regalado
06/12/2023, 5:11 AM Copy code
1, 503
2, 103229a
Amatya Avadhanula
06/12/2023, 5:11 AMOh, overreplication is not the problem here then
Amatya Avadhanula
06/12/2023, 5:14 AMonly these 3 log linesAre these the only 3 log lines in total? I interpreted it as these 3 log lines are repeated continuously on the historical earlier
v
victor regalado
06/12/2023, 5:17 AMI mean they are repeated per segment
victor regalado
06/12/2023, 4:06 PMDo you have any insight on
org.apache.druid.server.coordinator.ReplicationThrottler:victor regalado
06/12/2023, 10:36 PMReplicant create queue stuck after 3 runs