Overlord startup exception

[Geoffrey Cheng]

From the batch loading page (http://druid.io/docs/latest/tutorials/tutorial-loading-batch-data.html), it seems that the MiddleManager instance is not explicitly needed to run indexing tasks.

So I have my coordinator, realtime, historical, broker, and the overlord all running, and it works with the real-time mode.  During startup of overlord, however, the following error appears - Is this harmless?

2015-10-22T05:21:15,861 DEBUG [main] org.eclipse.jetty.util.component.AbstractLifeCycle - STARTED @8527ms com.google.inject.servlet.GuiceFilter-5a7e7376

2015-10-22T05:21:15,861 DEBUG [main] org.eclipse.jetty.servlet.FilterHolder - Filter.init com.google.inject.servlet.GuiceFilter@11cbcf19

2015-10-22T05:21:15,883 CONFIG [main] com.sun.jersey.spi.service.ServiceFinder - Running in a non-OSGi environment

2015-10-22T05:21:15,953 CONFIG [main] com.sun.jersey.server.impl.ejb.EJBComponentProviderFactoryInitilizer - The EJB interceptor binding API is not available. JAX-RS EJB support is disabled.

javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial

        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) ~[?:1.7.0_85]

        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) ~[?:1.7.0_85]

        at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:344) ~[?:1.7.0_85]

        at javax.naming.InitialContext.lookup(InitialContext.java:411) ~[?:1.7.0_85]

        at com.sun.jersey.server.impl.ejb.EJBComponentProviderFactoryInitilizer.initialize(EJBComponentProviderFactoryInitilizer.java:64) [jersey-servlet-1.19.jar:1.19]

        at com.sun.jersey.spi.container.servlet.WebComponent.configure(WebComponent.java:570) [jersey-servlet-1.19.jar:1.19]

        at com.sun.jersey.spi.container.servlet.ServletContainer$InternalWebComponent.configure(ServletContainer.java:332) [jersey-servlet-1.19.jar:1.19]

        at com.sun.jersey.spi.container.servlet.WebComponent.load(WebComponent.java:604) [jersey-servlet-1.19.jar:1.19]

        at com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:207) [jersey-servlet-1.19.jar:1.19]

        at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:394) [jersey-servlet-1.19.jar:1.19]

        at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:577) [jersey-servlet-1.19.jar:1.19]

        at javax.servlet.GenericServlet.init(GenericServlet.java:244) [javax.servlet-api-3.1.0.jar:3.1.0]

        at com.google.inject.servlet.ServletDefinition.init(ServletDefinition.java:119) [guice-servlet-4.0-beta.jar:?]

        at com.google.inject.servlet.ManagedServletPipeline.init(ManagedServletPipeline.java:84) [guice-servlet-4.0-beta.jar:?]

        at com.google.inject.servlet.ManagedFilterPipeline.initPipeline(ManagedFilterPipeline.java:104) [guice-servlet-4.0-beta.jar:?]

        at com.google.inject.servlet.GuiceFilter.init(GuiceFilter.java:224) [guice-servlet-4.0-beta.jar:?]

        at org.eclipse.jetty.servlet.FilterHolder.initialize(FilterHolder.java:138) [jetty-servlet-9.2.5.v20141112.jar:9.2.5.v20141112]

        at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:852) [jetty-servlet-9.2.5.v20141112.jar:9.2.5.v20141112]

        at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298) [jetty-servlet-9.2.5.v20141112.jar:9.2.5.v20141112]

        at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741) [jetty-server-9.2.5.v20141112.jar:9.2.5.v20141112]

Geoff

[Gian Merlino]

I'm not really sure what that means, but if things still work even after that message, then that's great :P

Do you mind filing a github issue with this exception message, the version of druid you're using, the command you're using to start up the overlord, and whether or not things do seem to work properly after the message gets printed?

--
You received this message because you are subscribed to the Google Groups "Druid User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+...@googlegroups.com.
To post to this group, send email to druid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/c2126f76-d5ce-45f7-9b55-30ef5d0b391b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Geoffrey Cheng]

ok I will do that