| Summary | Node daemon constantly re-registers with the Locator |
|---|---|
| Article Number | 14668 |
| Environment | All Supported Operating Systems Orbix 6.3.4 |
| Question/Problem Description | Node daemon constantly re-registers with the Locator. Locator log reveals that node daemons are re-registering every minute with the Locator: Mon, 17 May 2010 08:20:59.0000000 [localhost:696] (IT_LOCATOR:95) I - Node daemon registered, name: iona_services.node_daemon.localhost Mon, 17 May 2010 08:21:50.0000000 [localhost:696] (IT_LOCATOR:95) I - Node daemon registered, name: iona_services.node_daemon.localhost Mon, 17 May 2010 08:22:40.0000000 [localhost:696] (IT_LOCATOR:95) I - Node daemon registered, name: iona_services.node_daemon.localhost Mon, 17 May 2010 08:23:25.0000000 [localhost:696] (IT_LOCATOR:95) I - Node daemon registered, name: iona_services.node_daemon.localhost Mon, 17 May 2010 08:24:15.0000000 [localhost:696] (IT_LOCATOR:95) I - Node daemon registered, name: iona_services.node_daemon.localhost Mon, 17 May 2010 08:25:00.0000000 [localhost:696] (IT_LOCATOR:95) I - Node daemon registered, name: iona_services.node_daemon.localhost Mon, 17 May 2010 08:25:45.0000000 [localhost:696] (IT_LOCATOR:95) I - Node daemon registered, name: iona_services.node_daemon.localhost Mon, 17 May 2010 08:26:35.0000000 [localhost:696] (IT_LOCATOR:95) I - Node daemon registered, name: iona_services.node_daemon.localhost |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | This can be caused by the heartbeat configuration between node daemon and locator being changed in a way that plugins:node_daemon:heartbeat_interval_timeout < plugins:locator:node_daemon_heartbeat_interval. The first variable plugins:node_daemon:heartbeat_interval_timeout (specified in the node daemon's configuration scope) specifies, in seconds, the interval a node daemon expects to receive a heartbeat message from a locator. If no heartbeat is received in this interval the node daemon attempts to register with the locator again. The default is 40 seconds. The second variable plugins:locator:node_daemon_heartbeat_interval (specified in the locators configuration scope) specifies, in seconds, the interval between heartbeat messages sent by the locator to its node daemons. This is used to detect the failure of a node daemon. The default interval is 30 seconds. Hence, if the node daemon times out waiting for the locator's heartbeat before the locator sends its heartbeat message to the node daemon, the node daemon will try to re-register with the locator. This should not cause any immediate problems, however this constant re-registration imposes additional load on both locator and node daemon processes and should be avoided. |
| Resolution | If not needed, don't change the default values of these two configuration variables. They should be sufficient for most applications. If it is necessary to change these variables, then it must be ensured that plugins:node_daemon:heartbeat_interval_timeout > plugins:locator:node_daemon_heartbeat_interval. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 23 June 2012 |
| First Published date: | 10 September 2011 |
#KnowledgeDocs
#Orbix
