Druid co-ordinator not found error

Apache Druid Q&A Google Groups
#1

2016-01-18T09:12:17,994 ERROR [coordinator_handoff_scheduled_0] io.druid.curator.discovery.ServerDiscoverySelector - No server instance found

2016-01-18T09:12:17,994 ERROR [coordinator_handoff_scheduled_0] io.druid.segment.realtime.plumber.CoordinatorBasedSegmentHandoffNotifier - Exception while checking handoff for dataSource[netflow] Segment[SegmentDescriptor{interval=2016-01-18T09:09:00.000Z/2016-01-18T09:10:00.000Z, version=‘2016-01-18T09:09:00.000Z’, partitionNumber=0}], Will try again after [60000]secs

com.metamx.common.ISE: Cannot find instance of coordinator

at io.druid.client.coordinator.CoordinatorClient.baseUrl(CoordinatorClient.java:108) ~[druid-server-0.8.3-rc4.jar:0.8.3-rc4]

at io.druid.client.coordinator.CoordinatorClient.fetchServerView(CoordinatorClient.java:74) ~[druid-server-0.8.3-rc4.jar:0.8.3-rc4]

at io.druid.segment.realtime.plumber.CoordinatorBasedSegmentHandoffNotifier.checkForSegmentHandoffs(CoordinatorBasedSegmentHandoffNotifier.java:101) [druid-server-0.8.3-rc4.jar:0.8.3-rc4]

at io.druid.segment.realtime.plumber.CoordinatorBasedSegmentHandoffNotifier$1.run(CoordinatorBasedSegmentHandoffNotifier.java:86) [druid-server-0.8.3-rc4.jar:0.8.3-rc4]

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:1.8.0_66]

at java.util.concurrent.FutureTask.runAndReset(Unknown Source) [?:1.8.0_66]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) [?:1.8.0_66]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:1.8.0_66]

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_66]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_66]

at java.lang.Thread.run(Unknown Source) [?:1.8.0_66]

Currently running 0.8.3-rc4. No idea what I’m missing.

#2

Found the issue. The following needs to be added: to the config/_common/common.runtime.properties file
druid.selectors.coordinator.serviceName=coordinator

#3

druid.selectors.coordinator.serviceName=coordinator

2016-01-18T09:12:17,994 ERROR [coordinator_handoff_scheduled_0] io.druid.curator.discovery.ServerDiscoverySelector - No server instance found

2016-01-18T09:12:17,994 ERROR [coordinator_handoff_scheduled_0] io.druid.segment.realtime.plumber.CoordinatorBasedSegmentHandoffNotifier - Exception while checking handoff for dataSource[netflow] Segment[SegmentDescriptor{interval=2016-01-18T09:09:00.000Z/2016-01-18T09:10:00.000Z, version=‘2016-01-18T09:09:00.000Z’, partitionNumber=0}], Will try again after [60000]secs

com.metamx.common.ISE: Cannot find instance of coordinator

at io.druid.client.coordinator.CoordinatorClient.baseUrl(CoordinatorClient.java:108) ~[druid-server-0.8.3-rc4.jar:0.8.3-rc4]

at io.druid.client.coordinator.CoordinatorClient.fetchServerView(CoordinatorClient.java:74) ~[druid-server-0.8.3-rc4.jar:0.8.3-rc4]

at io.druid.segment.realtime.plumber.CoordinatorBasedSegmentHandoffNotifier.checkForSegmentHandoffs(CoordinatorBasedSegmentHandoffNotifier.java:101) [druid-server-0.8.3-rc4.jar:0.8.3-rc4]

at io.druid.segment.realtime.plumber.CoordinatorBasedSegmentHandoffNotifier$1.run(CoordinatorBasedSegmentHandoffNotifier.java:86) [druid-server-0.8.3-rc4.jar:0.8.3-rc4]

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:1.8.0_66]

at java.util.concurrent.FutureTask.runAndReset(Unknown Source) [?:1.8.0_66]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) [?:1.8.0_66]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:1.8.0_66]

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_66]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_66]

at java.lang.Thread.run(Unknown Source) [?:1.8.0_66]

Currently running 0.8.3-rc4. No idea what I’m missing.

Found the issue. The following needs to be added: to the config/_common/common.runtime.properties file

Thanks for the tip. I’ve updated error message for this case to include “druid.selectors.coordinator.serviceName”.

2016년 1월 18일 월요일 오후 6시 41분 21초 UTC+9, Arun Pereira 님의 말:

#4

I added this to my config by my broker has error:

druid.selectors.coordinator.serviceName=druid/coordinator

ERROR [main] org.apache.druid.curator.discovery.ServerDiscoverySelector - No server instance found for [druid/coordinator]

could you please send your broker node config?

#5

Are they all talking to same zookeeper?

#6

yes. Zookeeper is on Master server.

#7

I have this error on my Data server too. all nodes on cluster cant connect to coordinator and overlord.

The IP don’t set and they use 127.0.0.1 instead of the correct IP.

I don’k know which config is missing.

#8

I just made a mistake.

I dont set the zookeeper correctly.