You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (Jira)" <ji...@apache.org> on 2025/08/06 11:06:00 UTC
[jira] [Resolved] (SLING-12870) Introduce offline mode to discovery-standalone
[ https://issues.apache.org/jira/browse/SLING-12870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli resolved SLING-12870.
---------------------------------
Fix Version/s: Discovery Standalone 1.0.4
Resolution: Fixed
[PR|https://github.com/apache/sling-org-apache-sling-discovery-standalone/pull/1] merged - thx [~ionutpirlogea] - marking as resolved.
> Introduce offline mode to discovery-standalone
> ----------------------------------------------
>
> Key: SLING-12870
> URL: https://issues.apache.org/jira/browse/SLING-12870
> Project: Sling
> Issue Type: Task
> Components: Discovery
> Reporter: Ionut Pirlogea
> Assignee: Ionut Pirlogea
> Priority: Major
> Fix For: Discovery Standalone 1.0.4
>
>
> Sling jobs get executed in pods that don't belong to an active deployment.
> This poses the risk that these pods get overburdened and thus their health checks fail, which leads to a failing deployment.
> A new offline mode should be added to discovery-standalone : in this mode no topology would be ever established, discovery would report being offline. This also implies that no TOPOLOGY_INIT is ever sent to the TopologyEventListeners.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)