karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Branislav Kalas (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-4874) Distributed log service no order of messages, no serialization
Date Thu, 01 Dec 2016 08:45:58 GMT
Branislav Kalas created KARAF-4874:
--------------------------------------

             Summary: Distributed log service no order of messages, no serialization
                 Key: KARAF-4874
                 URL: https://issues.apache.org/jira/browse/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 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.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message