Branislav Kalas created KARAF-4874:

             Summary: Distributed log service no order of messages, no 
                 Key: KARAF-4874
             Project: Karaf
          Issue Type: Bug
          Components: cellar-core
    Affects Versions: cellar-4.0.2
            Reporter: Branislav Kalas

Cluster log writes records to hazelcast map with ClusterLogRecord instances as 
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.

This message was sent by Atlassian JIRA

Reply via email to