Hi,
On 15 March 2017 at 08:47, Andrea Aime <[email protected]> wrote:
> On Wed, Mar 15, 2017 at 8:48 AM, Luca Morandini <[email protected]>
> wrote:
>
>> > I don't know about the specific error, but the documentation clearly
>> indicates
>> > that a reload should never be used along with the JMS clustering
>> > extension:
>>
>> Well, it says that hitting "Reload" would trigger the complete rebuild of
>> all
>> resources on the slaves, which would be fine when adding empty instances
>> to the
>> cluster, I supposed.
>>
>
> When it says "things to avoid" it really means it, I had data dirs busted
> by doing
> that by accident (training setup, I was not aware the clustering was
> already on
> while doing the basic parts and hitting reload willy-nilly...)
>
I also interpreted that documentation as being "it will take ages" rather
than "it will break things".
*Presumably* stopping & starting the master instance will effectively
trigger a complete rebuild of all slave resources too during catalog
startup? Or is reload special somehow?
Thanks,
Rob :)
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
