Clustering is using lite events for routing table caches
Description
The ClusterListener class should not use lite events when adding MapListeners. Lite events will not transfer the old and new values of map entries (when they are added/updated/deleted). Therefore, when using lite events the ClusterListener will fail. This is a very important limitation since caches in the routing table couldn't be distributed since new/old values will not be present in events. That is why we need to stop using lite events so that caches of the routing table could be of type distributed. Having routing table caches distributed will let the server scale to unlimited numbers.
The ClusterListener class should not use lite events when adding MapListeners. Lite events will not transfer the old and new values of map entries (when they are added/updated/deleted). Therefore, when using lite events the ClusterListener will fail. This is a very important limitation since caches in the routing table couldn't be distributed since new/old values will not be present in events. That is why we need to stop using lite events so that caches of the routing table could be of type distributed. Having routing table caches distributed will let the server scale to unlimited numbers.