Disable Discovery Service

Avatar

Avatar

ronnyfm

Avatar

ronnyfm

ronnyfm

24-05-2017

I am facing this WARN message that slows down the instance. For some reason the cluster change event keeps updating and changing. 

Is there a way to disable this service or configuration for a single instance that is not in a cluster? Already tried removing the default localhost topology URL.

org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler checkForLocalClusterViewChange/.run: time since local instance last wrote a heartbeat is 669667ms (heartbeatTimeoutMillis=300000, heartbeatIntervalMillis=30000 => maxMillisSinceHb=240000). Flagging us as (still) changing 24.05.2017 09:22:51.868 *INFO* [discovery.connectors.common.runner.f706cedf-cb2a-4421-8e65-d2f62b3daa23.checkForLocalClusterViewChange] org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler invalidateCurrentEstablishedView: invalidating slingId=f706cedf-cb2a-4421-8e65-d2f62b3daa23, lastEstablishedViewId=f6e47254-570f-43ed-ac54-70d77e2885cb

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

yogirajm6444110

Avatar

yogirajm6444110

yogirajm6444110

13-06-2017

To recover this , you need to do graceful rolling restart , it will recover from the red topology .

Answers (4)

Answers (4)

Avatar

Avatar

ronnyfm

Avatar

ronnyfm

ronnyfm

30-06-2017

Well, that didn't solve the issue. The only workaround was to increase timeouts in the configuration.

Avatar

Avatar

MC_Stuff

Avatar

MC_Stuff

MC_Stuff

24-05-2017

Hi ronny, 

Install the standalone sling discovery bundle 

Thanks,