Ticket 8475 - Requested Fields for ElasticSearch
Summary: Requested Fields for ElasticSearch
Status: OPEN
Alias: None
Product: Slurm
Classification: Unclassified
Component: Accounting (show other tickets)
Version: 24.05.x
Hardware: Linux Linux
: 5 - Enhancement
Assignee: Alejandro Sanchez
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2020-02-10 09:15 MST by HMS Research Computing
Modified: 2024-04-04 05:26 MDT (History)
3 users (show)

See Also:
Site: Harvard Medical School
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---


Attachments

Note You need to log in before you can comment on or make changes to this ticket.
Description HMS Research Computing 2020-02-10 09:15:38 MST
Hi,

We would like request new fields to be added to the ElasticSearch plugin so that we can do better long accounting for our jobs.

The fields we would like are:


— Critical to  have:
MaxRSS
ReqMem
TotalCPU

— Would really like to have:
MaxDiskRead
MaxDiskWrite
MaxVMSize
ReqTres

— Nice to have:
AllocGRES
AllocTres
MaxPages
Priority
SystemCPU

Kind Regards
--Mick
Comment 1 Jason Booth 2020-02-10 09:26:49 MST
Hi Mick - We received your feature request. We currently do not have plans to expand this right now. Normally features like these are paid engagements. Is this something that your site would like to sponsor?
Comment 2 HMS Research Computing 2020-02-11 09:02:38 MST
Hi Jason,

I need to talk to my team and see how to proceed. I'll follow-up in a few days.

--Mick
Comment 4 Jason Booth 2020-02-11 10:45:58 MST
Hi Mick - I have discussed this feature request internally and we believe we can accommodate this request without any sponsorship from your end, although it would have to be part of 20.11 or later. We will keep you posted on the slated release.
Comment 5 HMS Research Computing 2020-02-11 12:47:48 MST
(In reply to Jason Booth from comment #4)
> Hi Mick - I have discussed this feature request internally and we believe we
> can accommodate this request without any sponsorship from your end, although
> it would have to be part of 20.11 or later. We will keep you posted on the
> slated release.

Hi Jason,

That's great, please let me know an ETA and I'll watch for new releases. We do plan to upgrade later this year and we'll probably wait until this feature-set is included, unless you advise otherwise.

Kind regards
--Mick
Comment 6 Jason Booth 2020-02-11 13:06:55 MST
Mick,

>We do plan to upgrade later this year and we'll probably wait until this feature-set is included, unless you advise otherwise.

20.02 will be released very soon so you will want to upgrade to at least 19.05 to stay within our support model. When 20.02 is released 18.08 will no longer receive support. 

In regards to the timeline, that will have to wait until after we release 20.02 since we are working on getting that release out the door.
Comment 7 HMS Research Computing 2020-05-06 08:05:21 MDT
Hi Jason,

We're working on upgrading our Slurm instance real soon now. Do you expect these ES features in an upcoming release?

Thanks
--Mick
Comment 14 Karun 2021-04-08 13:29:18 MDT
Hi Jason,

Was this implemented in 20.11, I didn't find any specifics in release notes.

Thanks!
Comment 15 HMS Research Computing 2024-04-01 10:45:22 MDT
Any progress on this?

Thanks
--Mick
Comment 19 Alejandro Sanchez 2024-04-04 05:26:00 MDT
Hi,

To summarize:

tres_[alloc|req] fields are available since Slurm 20.11.0 (commit 564768643a).
tres_[alloc|req]_raw fields are available since Slurm 23.11.1 (commit a53d2afa3e).
priority will be available since the next Slurm major release (commit d02c4d65cf).

We discarded adding a separate field analogous to what sacct displays for ReqMem since that info could be derived from tres_req[_raw].

The addition of the above fields are natural additions in concordance of the jobcomp plugin design, meaning they are accessible from the job_record_t structure handed to its interface.

Unfortunately, the rest of the requested fields can't directly be added as their information is not part of the job_record_t, but instead derived from slurmdb_stats_t, slurmdb_job_rec_t or various slurmdb_step_rec_t aggregations, which are structs designed to work with the accounting_storage plugins and sacct client-side.

Making them available to the jobcomp plugins would fall out of the scope of this bug. They could get potentially added in the future, but it'd require refactor the jobcomp plugin interface to make this universally available instead of splitting it up, and that's a bunch more work, so would fall under RFE territory.

Please, let us know if you need anything else from this bug. Otherwise, I'll go ahead and tag it as resolved. And sorry this took a little longer than expected.