This message was deleted.
# troubleshooting
s
This message was deleted.
r
I am not sure how to do that, could you please let me know how/where to do the same
should i be adding like this for clarity?
Copy code
druid.extensions.loadList=["druid-hdfs-storage"]
i couldn't find clarity emitter extension name in the doc here though- https://druid.apache.org/docs//0.15.1-incubating/development/extensions.html#core-extensions
b
I have the following:
Copy code
druid.monitoring.monitors=["org.apache.druid.java.util.metrics.JvmMonitor","org.apache.druid.java.util.metrics.JvmThreadsMonitor"]

druid.emitter.composing.emitters=["logging","clarity"]

druid.emitter=composing
druid.emitter=clarity
you have to add that in
Copy code
druid.extensions.loadList=["clarity-emitter"]
Does it work for you ?
r
ok thanks, let me try this, will take a while for deployment process, will acknowledge back
👀 1
b
BTW, if you are using Clarity, you should log a ticket with Imply Support as well
👍 1
r
@Brandon Tan after deploying this change, still i am getting error in druid-historical node. added this config - druid.extensions.loadList=["druid-s3-extensions", "mysql-metadata-storage", "druid-datasketches", "druid-prometheus-emitter", "clarity-emitter"]
Copy code
com.tubemogul.druid.query.zerofilledtopn.ZeroFilledTopNQueryModule -> com.google.inject.multibindings.MapBinder$RealMapBinder)
  while locating java.util.Map<java.lang.Class<? extends org.apache.druid.query.Query>, org.apache.druid.query.QueryToolChest>
    for the 1st parameter of org.apache.druid.query.MapQueryToolChestWarehouse.<init>(MapQueryToolChestWarehouse.java:35)
  while locating org.apache.druid.query.MapQueryToolChestWarehouse
  while locating org.apache.druid.query.QueryToolChestWarehouse
    for the 1st parameter of org.apache.druid.server.QueryLifecycleFactory.<init>(QueryLifecycleFactory.java:52)
  at org.apache.druid.server.QueryLifecycleFactory.class(QueryLifecycleFactory.java:52)
  while locating org.apache.druid.server.QueryLifecycleFactory
    for the 1st parameter of org.apache.druid.server.QueryResource.<init>(QueryResource.java:113)
  at org.apache.druid.server.QueryResource.class(QueryResource.java:78)
  while locating org.apache.druid.server.QueryResource
  while locating org.apache.druid.server.metrics.QueryCountStatsProvider
    for the 1st parameter of org.apache.druid.server.metrics.QueryCountStatsMonitor.<init>(QueryCountStatsMonitor.java:40)
  while locating org.apache.druid.server.metrics.QueryCountStatsMonitor
  at org.apache.druid.server.metrics.MetricsModule.getMonitorScheduler(MetricsModule.java:92) (via modules: com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> org.apache.druid.server.metrics.MetricsModule)
  at org.apache.druid.server.metrics.MetricsModule.getMonitorScheduler(MetricsModule.java:92) (via modules: com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> org.apache.druid.server.metrics.MetricsModule)
  while locating org.apache.druid.java.util.metrics.MonitorScheduler
  at org.apache.druid.server.metrics.MetricsModule.configure(MetricsModule.java:77) (via modules: com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> org.apache.druid.server.metrics.MetricsModule)
  while locating org.apache.druid.java.util.metrics.MonitorScheduler annotated with @com.google.inject.name.Named(value=ForTheEagerness)

5 errors
	at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:470)
	at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:184)
	at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:110)
	at com.google.inject.Guice.createInjector(Guice.java:99)
b
1. What’s your deployment environment like ? 2. What version are you running ? 3. I assume this is on-prem Clarity. Would SaaS Clarity be an option for you ?
r
1. What’s your deployment environment like ? - K8 2. What version are you running ? 0.15.1-incubating apis 3. I assume this is on-prem Clarity. Would SaaS Clarity be an option for you ? in production with ec2 instane it works, but with k8 deployment we are getting this error
b
A client has similar issue ( K8s as well ) and they resolved it thru Support. So you may want to consider that route if you are an Imply customer
r
okay, thanks