On 15 March 2017 at 11:29, Andrea Aime <[email protected]> wrote:
> On Wed, Mar 15, 2017 at 12:15 PM, Robert Coup <[email protected]
> > wrote:
>
>> 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".
>>
>
> Pull requests to reword that welcomed :-p
>
I can.
Current wording is a bit more bold that I remember:
*NEVER RELOAD THE GEOSERVER CATALOG ON A MASTER:* Each master instance
should never call the catalog reload since this propagates the creation of
all the resources, styles, etc to all the connected slaves.
Followup question:
With a master-writes and shared data-directory/DB approach... restarting
the master seems fine. But reloading will cause issues? Making some
assumptions:
1. reload doesn't pass a "destroy" message across the cluster, so on a
slave everything is created on top of the previous objects?
2. normal webapp startup suppresses create messages across the cluster?
But if you have slaves that can write to a shared data-directory/DB, seems
like *any* catalog edits will make you have a bad day?
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
