Druid-services-0.6.154 start-up issue

Today ,Start druid service,data can‘t save ,this log:
broker.log:

02:30:45] WARN retry.ExponentialBackoffRetry “maxRetries too large (30). Pinning to 29”

Jan 13, 2016 2:30:53 AM com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register

INFO: Registering com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider as a provider class

Jan 13, 2016 2:30:53 AM com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register

INFO: Registering io.druid.server.StatusResource as a root resource class

Jan 13, 2016 2:30:53 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate

INFO: Initiating Jersey application, version ‘Jersey: 1.17.1 02/28/2013 12:47 PM’

Jan 13, 2016 2:30:54 AM com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory getComponentProvider

INFO: Binding com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider to GuiceManagedComponentProvider with the scope “Singleton”

Jan 13, 2016 2:30:59 AM com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory getComponentProvider

INFO: Binding io.druid.server.QueryResource to GuiceInstantiatedComponentProvider

Jan 13, 2016 2:30:59 AM com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory getComponentProvider

INFO: Binding io.druid.server.ClientInfoResource to GuiceInstantiatedComponentProvider

Jan 13, 2016 2:30:59 AM com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory getComponentProvider

INFO: Binding io.druid.server.StatusResource to GuiceManagedComponentProvider with the scope “Undefined”

Hi,
these log entries seem normal, Can you share Full log , runtime.props and the command used to start the broker ?

Also, is this anew setup or was it running previously and just failing on a broker restart ?

If you are trying to setup a new cluster, I would recommend using the latest druid stable instead of 0.6.154 as its quite old release.

There are a huge number of performance and stability improvements since the 0.6.x branch.