[
https://issues.apache.org/jira/browse/SLING-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092537#comment-14092537
]
Ashutosh Shroti commented on SLING-3652:
----------------------------------------
[~cziegeler] When instance started up in a cluster, changes in configuration of
one instance are getting distributed to others by default (though the default
value of "distribute config" is false if look at felix console).
After re-setting this config (set true & the false) will actually help us to
stop distribution of the configuration changes across instances, which is an
un-necessary step in my opinion.
[~amitgupt] has also reproduced this issue along with me, what is your input on
this?
> 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)
