Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Disable Discovery Service

Avatar

Level 4

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
1 Accepted Solution

Avatar

Correct answer by
Former Community Member

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

View solution in original post

5 Replies

Avatar

Level 9

Hi ronny, 

Install the standalone sling discovery bundle 

Thanks,

Avatar

Correct answer by
Former Community Member

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

Avatar

Level 4

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

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----