Just thought i'd poke this and see if there is any feedback. Another detail here - we are using the rest API to remove the layer\style.
On Wed, Jul 10, 2019 at 1:22 PM Jason Cradit <jasoncra...@gmail.com> wrote: > Hey All, > > We are using the HZ Clustering extension and it's gone quite well. We did > run into a problem around deleting styles and layers. It seems to allow > the delete well, but doesn't sync the delete to the others in the cluster. > So, then a catalog refresh is required. Was wondering if anyone else has > seen this and if there is a configuration problem that I need to resolve to > allow for this. We are in AWS and using EFS a shared data directory. Only > have 3 in the cluster currently and all look to be healthy and able to > communicate with each other. > > Thanks, > Jason > > We do run into this error as well: > > 2019-07-09 18:46:42,472 WARN [cluster.hazelcast] - 10.2.2.245:5701 - > Event dispatch failed: REMOVE (/10.2.2.24:5701) > [uuid:4efd2fe1-81f0-485d-a52e-9acb42d35d17, object > id:StyleInfo.600ff7c7-c164-4cb3-84c3-0c54cef71216, name:Rich Test App] > > java.lang.reflect.InvocationTargetException > > at sun.reflect.GeneratedMethodAccessor400.invoke(Unknown Source) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:498) > > at > org.geoserver.cluster.hazelcast.EventHzSynchronizer.processCatalogEvent(EventHzSynchronizer.java:262) > > at > org.geoserver.cluster.hazelcast.EventHzSynchronizer.processEvent(EventHzSynchronizer.java:172) > > at > org.geoserver.cluster.hazelcast.HzSynchronizer$EventWorker.call(HzSynchronizer.java:136) > > at > org.geoserver.cluster.hazelcast.HzSynchronizer$EventWorker.call(HzSynchronizer.java:121) > > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > > at java.lang.Thread.run(Thread.java:748) > > Caused by: java.lang.NullPointerException > > at com.sun.proxy.$Proxy30.hashCode(Unknown Source) > > at java.util.HashMap.hash(HashMap.java:339) > > at java.util.HashMap.remove(HashMap.java:799) > > at org.geoserver.catalog.ResourcePool.clear(ResourcePool.java:2028) > > at > org.geoserver.catalog.ResourcePool$CacheClearingListener.visit(ResourcePool.java:2463) > > at > org.geoserver.cluster.hazelcast.RemovedObjectProxy.proxyVisitory(RemovedObjectProxy.java:140) > > at > org.geoserver.cluster.hazelcast.RemovedObjectProxy.invoke(RemovedObjectProxy.java:103) > > at com.sun.proxy.$Proxy30.accept(Unknown Source) > > at > org.geoserver.catalog.ResourcePool$CacheClearingListener.handleRemoveEvent(ResourcePool.java:2432) > > ... 13 more >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
