[
https://issues.apache.org/jira/browse/SLING-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090749#comment-14090749
]
Carsten Ziegeler commented on SLING-3652:
-----------------------------------------
[~shroti] thanks for the info. The JobConsumerManager has a configuration
property org.apache.sling.installer.configuration.persist with the default
value false. It is displayed in the web console with "Distribute config".
On a first startup, there is no configuration for the consumer manager;
therefore the configuration can't be distributed.
If you know change the config in the web console and don't change the
"Distribute config" setting, a configuration will be created with your changed
config and this value being set to false. Which then means, the config is not
distributed.
If you should happen a config on first startup, make sure that this field is
set to false in that config
So I think it works as it should
> Sling Job Consumer Manager : Distribute config should be disabled by default
> ----------------------------------------------------------------------------
>
> Key: SLING-3652
> URL: https://issues.apache.org/jira/browse/SLING-3652
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Event 3.3.10
> Reporter: Ashutosh Shroti
> Assignee: Amit Gupta
>
> Sling Job Consumer Manager service have an following flag:
> Distribute config -> disabled
> This should be disabled by default.
> Use Case: While configuring author instances in the cluster, config changes
> like disable the listener on topic "com/adobe/granite/workflow/offloading"
> should be local to an instance. Hence above mentioned flag should be disabled
> by default to prevent config changes to local instance.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
