There is another option to avoid extra effort when running within Sling. Have an optional implementation which makes use of SlingSettingsService to get fetch SlingId. With little bit of OSGi kung fu you can have an implementation which uses SlingId when running in Sling otherwise maintains its own id using File based approach.
This would reduce operational complexity Chetan Mehrotra On Wed, Nov 25, 2015 at 6:23 PM, Stefan Egli <stefane...@apache.org> wrote: > Right, I'm not sure it is indeed a requirement. But without automatic > support it might get forgotten and thus the cluster id would change upon > failover. > > Cheers, > Stefan > > On 25/11/15 13:40, "Chetan Mehrotra" <chetan.mehro...@gmail.com> wrote: > >>On Wed, Nov 25, 2015 at 6:00 PM, Stefan Egli <stefane...@apache.org> >>wrote: >>>> * disadvantage: cold standby would require an explicit copying of this >>>>file >>>> (during initial hand-shake?) >> >>Why is that a requirement? Cold standby is just a backup and currently >>there is no automatic failover support. >> >>For such cases we can allow passing the id as a system/framework property >>also >> >>Chetan Mehrotra > >
