Error in Indexing service.

I am getting errors in overlord service task while task is marked as SUCCESS. I have 3 middle managers running with default worker size if that matters. 

I think because of this error segments are not saved in S3 and mysql metadata is not updated.

Please help or provide some help to troubleshoot this error. Attached are detailed task logs.

2016-02-04T22:15:00,566 ERROR [Thread-42] com.metamx.common.lifecycle.Lifecycle$AnnotationBasedHandler - Exception when stopping method[public void io.druid.curator.discovery.ServerDiscoverySelector.stop() throws java.io.IOException] on object[io.druid.curator.discovery.ServerDiscoverySelector@7499eac7]
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_72]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_72]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_72]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_72]
	at com.metamx.common.lifecycle.Lifecycle$AnnotationBasedHandler.stop(Lifecycle.java:337) [java-util-0.27.4.jar:?]
	at com.metamx.common.lifecycle.Lifecycle.stop(Lifecycle.java:261) [java-util-0.27.4.jar:?]
	at io.druid.cli.CliPeon$2.run(CliPeon.java:220) [druid-services-0.8.2.jar:0.8.2]
	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_72]
Caused by: java.lang.IllegalStateException: Already closed or has not been started
	at com.google.common.base.Preconditions.checkState(Preconditions.java:176) ~[guava-16.0.1.jar:?]
	at org.apache.curator.x.discovery.details.ServiceCacheImpl.close(ServiceCacheImpl.java:91) ~[curator-x-discovery-2.8.0.jar:?]
	at org.apache.curator.x.discovery.details.ServiceProviderImpl.close(ServiceProviderImpl.java:78) ~[curator-x-discovery-2.8.0.jar:?]
	at io.druid.curator.discovery.ServerDiscoverySelector.stop(ServerDiscoverySelector.java:98) ~[druid-server-0.8.2.jar:0.8.2]
	... 8 more

OverlordTaskLog.txt (2.49 MB)

Hey Karan,

I think this error is scary looking, but harmless. It should be fixed in a later version (I think there’s some stuff getting closed twice and that doesn’t happen anymore). But it isn’t causing your issues.

Perhaps check one of these things instead: https://github.com/druid-io/tranquility/blob/master/docs/trouble.md#no-data-is-showing-up-in-druid-even-though-events-seem-to-be-successfully-sent

Thanks Gian