Order of druid.extensions.loadList matters when using druid-kafka-extraction-namespace

[dclim]

When I had druid-lookups-cached-global before druid-kafka-extraction-namespace in my loadList, I would get the following bind error:

2016-10-05T17:43:00,647 ERROR [LookupCoordinatorManager--9] io.druid.server.lookup.cache.LookupCoordinatorManager - Error submitting to [http://davids-mbp:8400/druid/listen/v1/lookups]: {class=io.druid.server.lookup.cache.LookupCoordinatorManager, exceptionType=class java.io.IOException, exceptionMessage=Bad update request to [http://davids-mbp:8400/druid/listen/v1/lookups] : [500] : [Internal Server Error]  Response: [:)
���error�Guice configuration errors:

1) No implementation for io.druid.server.lookup.namespace.cache.NamespaceExtractionCacheManager was bound.
  while locating io.druid.server.lookup.namespace.cache.NamespaceExtractionCacheManager

1 error��]}
java.io.IOException: Bad update request to [http://davids-mbp:8400/druid/listen/v1/lookups] : [500] : [Internal Server Error]  Response: [:)
���error�Guice configuration errors:

1) No implementation for io.druid.server.lookup.namespace.cache.NamespaceExtractionCacheManager was bound.
  while locating io.druid.server.lookup.namespace.cache.NamespaceExtractionCacheManager

1 error��]
    at io.druid.server.lookup.cache.LookupCoordinatorManager.updateAllOnHost(LookupCoordinatorManager.java:228) ~[classes/:?]
    at io.druid.server.lookup.cache.LookupCoordinatorManager$5.run(LookupCoordinatorManager.java:371) [classes/:?]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_60]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_60]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_60]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_60]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_60]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_60]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_60]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_60]
    at java.lang.Thread.run(Thread.java:745) [?:1.8.0_60]

Everything worked as expected when druid-kafka-extraction-namespace loaded before druid-lookups-cached-global. Is anyone else seeing this?

[github-actions]

This issue has been marked as stale due to 280 days of inactivity.
It will be closed in 4 weeks if no further activity occurs. If this issue is still
relevant, please simply write any comment. Even if closed, you can still revive the
issue at any time or discuss it on the dev@druid.apache.org list.
Thank you for your contributions.

[github-actions]

This issue has been closed due to lack of activity. If you think that
is incorrect, or the issue requires additional review, you can revive the issue at
any time.