You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by "GaryChow-LGTM (via GitHub)" <gi...@apache.org> on 2025/03/17 08:18:58 UTC
[I] Druid Coordinator stop assign segments after the zk restart (druid)
GaryChow-LGTM opened a new issue, #17807:
URL: https://github.com/apache/druid/issues/17807
### Affected Version
Druid 25.0
### Description
1. Zookeeper restart due to the node crash in 05:50 UTC
2. Coordinator log
`2025-03-17T05:50:23,080 INFO [LeaderSelector[/druid/coordinator/_COORDINATOR]] org.apache.druid.server.coordinator.DruidCoordinator - I am no longer the leader...
2025-03-17T05:50:24,370 INFO [LeaderSelector[/druid/coordinator/_COORDINATOR]] org.apache.druid.server.coordinator.DruidCoordinator - I am the leader of the coordinators, all must bow! Starting coordination in [PT30S].`
3. There are no new segment assignments, but the following log is present with no error logs:
- `Polled and found 201 rule(s) for 193 datasource(s).`
I have attempted the following approaches to recover from the issue:
1. Restarted the coordinator leader and follower, but this did not help.
2. Restarted the Zookeeper follower, but this did not help.
3. Restarted the Zookeeper leader, which resolved the issue.
--
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: commits-unsubscribe@druid.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
Re: [I] Druid Coordinator stop assign segments after the zk restart (druid)
Posted by "gianm (via GitHub)" <gi...@apache.org>.
gianm commented on issue #17807:
URL: https://github.com/apache/druid/issues/17807#issuecomment-2768912510
It seems like some kind of issue with leader election. It's unfortunately hard to debug from just this provided information. It would possibly be helpful to see more logs. If this ever happens again, it's also possibly helpful to see a thread dump of the apparently-stuck Coordinator before restarting it.
--
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: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org