You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2023/04/06 09:43:00 UTC
[jira] [Updated] (YUNIKORN-1679) Re-write event storage from map to slice
[ https://issues.apache.org/jira/browse/YUNIKORN-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko updated YUNIKORN-1679:
-----------------------------------
Summary: Re-write event storage from map to slice (was: Re-write event storage from map to ringbuffer)
> Re-write event storage from map to slice
> ----------------------------------------
>
> Key: YUNIKORN-1679
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1679
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
> Labels: pull-request-available
>
> Currently, event objects stored in a map:
> {noformat}
> es.eventMap[event.ObjectID] = event
> {noformat}
> Publishing the events happens in every 2 seconds by default. The problem is, more than one event belonging to the same ObjectID can arrive, which means we end up losing events.
> They should be stored in a data structure which puts a cap on the number of events, but we can't lose them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org