Hi, Thank you all very much, we've got the same results, and now with the confirmation from community we could for sure take a look at different options.
Stepan вт, 20 нояб. 2018 г. в 01:57, Robert Munteanu <[email protected]>: > Ah, yes, that does makes sense. > > Thanks, > > Robert > > On Tue, 2018-11-20 at 09:31 +0000, Nicolas Peltier wrote: > > No i haven't tried that and I would not bet on it. > > I was referring to 2+ separate segment tar based instance that are > > written on with "broadcast" means like distribution. > > > > On 20/11/2018 10:11, "Robert Munteanu" <[email protected]> wrote: > > > > Hi, > > > > On Mon, 2018-11-19 at 16:11 +0000, Nicolas Peltier wrote: > > > Note that option 2 is the easiest option in case you are > > clustering > > > for read only (high availability scenario) > > > > If by 2 you mean " Segment Tar based deployment ( where two > > instances > > of Sling will use the same, mounted repository folder)" that was > > not > > possible last time I tried. > > > > The SegmentStore does not work on a read-only file-system as it > > eagerly > > aquires the journal lock and starts writing (IIRC) and also can't > > work > > with multiple processes sharing the same filesystem location. > > > > Did you manage to get this working at some point? > > > > Thanks, > > > > Robert > > > > > > > > >
