On 15/03/17 18:27, Andrea Aime wrote: > On Wed, Mar 15, 2017 at 5:50 AM, Luca Morandini > <[email protected] > <mailto:[email protected]>> wrote: > > Changing the catalog on the master causes the updates to be mirrored > faithfully on > the slaves; however, when the "Reload" button is hit on the master, this > exception > is raised on the slaves: > > 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. > I'm a bit surprised you did not end up ruining the slave's configuration... It was empty (separate data dirs), not much to ruin there. So, when adding a new instance, shall I stop accepting catalog changes, copy the data dir to the new instance, connect the new (slave) instance to the master, and then restart accepting catalog changes? Cheers, Luca Morandini Data Architect - AURIN project Melbourne eResearch Group Department of Computing and Information Systems Room 3.08. Level 3, Doug McDonell Building, Parkville Campus University of Melbourne Tel. +61 03 903 58 380 Skype: lmorandini LinkedIn: https://www.linkedin.com/in/lmorandini ------------------------------------------------------------------------------ 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
