[
https://issues.apache.org/jira/browse/YUNIKORN-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759599#comment-17759599
]
Craig Condit commented on YUNIKORN-1939:
----------------------------------------
I still think this is better done on the client.
If you have say, 10 clients, then doing this work on the server means you're
doing 10x the work, and scalability and performance of the server suffers.
However if the processing is done on the client, each client does 1X the work,
and the server does no additional work at all, which leads to better
scalability.
Start ID is easy - we already provide a usable starting point for clients by
retrieving a page of results. Clients can then keep requesting events until
they receive no more.
Filtering is also very simple on the client – simply throw away events that
don't match your filtering criteria. This also has the advantage of being able
to customize exactly how this filtering works for each client's need. Doing
this server-side requires all possible filters to be implemented at the server,
and if something is missing, the clients have to filter anyway.
> Add retrieving recent events to the REST interface
> --------------------------------------------------
>
> Key: YUNIKORN-1939
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1939
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
>
> Based on an internal discussion, we need to add an extra convenience features
> to the REST interface.
> We'd like to retrieve the recent "n" events: the implementation of this is
> not difficult. We calculate the startID based on how many events we want.
> Right now this cannot be done reliably because right after we determined the
> startID, new events can arrive, so the last "n" is no longer the last "n".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
