Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
cellar-4.0.2
-
None
Description
Cluster log writes records to hazelcast map with ClusterLogRecord instances as keys.
cluster:log-display then just iterates through keyset of this map and outputs records to console.
Result is log messages with no ordering (no relation to order of putting records to map) which i think is useless.
When map reaches its max allowed size, there is LRU eviction strategy defined, which is also incorrect (cause if you use cluster:display you use records withoud any order) and record is just deleted, there is no persistence.