coordinator.servicename for druid 0.8.3 upgrade

The documentation for druid.selectors.coordinator.serviceName says that it is needed only by realtime nodes for handoffs.
http://druid.io/docs/0.8.3/configuration/index.html

However, the release notes for 0.8.3 says that it is required in all nodes configs`.

  1. If it is needed by only realtime nodes, why the need to put in all nodes?

  2. the ‘runtime.properties’ file of my coordinator currently says:

druid.service=coordinator

so for upgrading to 0.8.3, will the druid.selectors.coordinator.serviceName value need to be:

druid.selectors.coordinator.serviceName = coordinator

or

druid.selectors.coordinator.serviceName = druid/coordinator

Thanks.

Prashant

Hi,

The documentation for druid.selectors.coordinator.serviceName says that it is needed only by realtime nodes for handoffs.
http://druid.io/docs/0.8.3/configuration/index.html

However, the release notes for 0.8.3 says that it is required in all nodes configs`.

https://github.com/druid-io/druid/releases

sorry, where you see that information that it is used by all nodes for 0.8.3 docs ?

  1. If it is needed by only realtime nodes, why the need to put in all nodes?
  1. the ‘runtime.properties’ file of my coordinator currently says:

druid.service=coordinator

so for upgrading to 0.8.3, will the druid.selectors.coordinator.serviceName value need to be:

if you call it coordinator so use this one.

Hi Slim,

sorry, where you see that information that it is used by all nodes for 0.8.3 docs ?

Its in the release notes.

Here is a screenshot:

https://www.evernote.com/l/AAk0-A1Mn6NKNZLgI1A5A5X6MToRMPjdUio

Thanks,

Prashant

Yep it looks like it is used by most of the druid nodes especially realtime nodes.
So setting it for all nodes is mandatory.

Thanks