You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/03/23 18:17:00 UTC
[jira] [Commented] (KARAF-4874) Distributed log service no order of
messages, no serialization
[ https://issues.apache.org/jira/browse/KARAF-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17307320#comment-17307320 ]
ASF subversion and git services commented on KARAF-4874:
--------------------------------------------------------
Commit 47730d1a797c7aab7a7da2f44a68f459fb9c4f38 in karaf-cellar's branch refs/heads/main from jbonofre
[ https://gitbox.apache.org/repos/asf?p=karaf-cellar.git;h=47730d1 ]
[KARAF-4874] Add comparable on the cluster log key
> 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
> Affects Versions: cellar-4.0.2
> Reporter: Branislav Kalas
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: cellar-4.2.1
>
>
> 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
(v8.3.4#803005)