QRDEL(1)

πŸ—‘οΈβœ¨ qrdel β€” NAME βœ¨πŸ—‘οΈ

okay bestie, meet qrdel πŸ’… β€” the Grid Engine command that deletes Grid Engine Advance Reservations (aka ARs, if you're in the group chat 🫢). She's giving cleanup crew energy and honestly? iconic.


πŸ“œ SYNTAX πŸ“œ

qrdel [-f] [-help] [-u wc_user_list] wc_ar_list

like… that's it. that's the whole vibe check. no cap. 🌸


πŸ’– DESCRIPTION πŸ’–

so qrdel is literally your girl for deleting one or more Advance Reservations (AR), and you can point at them either by numeric id or by name πŸŽ€.

here's the tea on who can delete what, because permissions are the whole plot:

  • a manager/operator can delete ARs belonging to any user πŸ‘‘
  • regular users can only delete their own ARs πŸ™ˆ

if a manager wants to delete somebody else's AR, she can just specify the AR id. but by default? qrdel wc_ar_name will only delete the ARs belonging to that user. and a manager can flex into another user's stuff via -u wc_user_list ✨.

now the important part, don't scroll past this 🚨:

jobs referring to an AR tagged for deletion will also be removed. the AR itself only gets removed once all jobs referring to it are gone from the Grid Engine database. so it's a whole chain reaction, bestie, not a one-and-done.

also qrdel deletes ARs in the order in which the AR identifiers are presented β€” first come, first yeeted πŸ’….

want the full lore on wc_user_list and wc_ar_list? go read sge_types(5) πŸ“š.


βš™οΈ OPTIONS βš™οΈ

  • -f β€” Force action. the AR and the jobs using the AR get deleted from the Grid Engine queuing system even if the sge_execd(8) controlling the AR jobs does not respond to the delete request sent by the sge_qmaster(8) 😭 like it just goes for it. but heads up: users who have neither Grid Engine manager nor operator status can only use -f for their own ARs πŸ™ˆ.
  • -help β€” prints a list of all options. she's helpful like that 🫢.
  • -u wc_user_list β€” deletes only those ARs which were submitted by users specified in the list of usernames πŸ‘₯. for managers, it's possible to use qrdel -u "*" to delete all ARs for all users 🌈 (yes, the whole thing, girl). to delete a specific AR for a user, a manager has to specify the user and the AR id. if no AR is specified, all ARs belonging to that user get deleted πŸ’€.
  • wc_ar_list β€” a list of ARs that should be deleted (either numeric or names assigned with qrsub -N) πŸŽ€.

🌿 ENVIRONMENT VARIABLES 🌿

  • SGE_ROOT β€” specifies the location of the Grid Engine standard configuration files πŸ“.
  • SGE_CELL β€” if set, specifies the default Grid Engine cell ✨. to address a Grid Engine cell qrdel uses (in the order of precedence):
    • The name of the cell specified in the environment variable SGE_CELL, if it is set.
    • The name of the default cell, i.e. default.
  • SGE_DEBUG_LEVEL β€” if set, specifies that debug information should be written to stderr πŸ›. in addition the level of detail in which debug information is generated is defined.
  • SGE_QMASTER_PORT β€” if set, specifies the tcp port on which the sge_qmaster(8) is expected to listen for communication requests πŸ“‘. most installations will use a service map entry for the service sge_qmaster instead of defining the port.

πŸ“‚ FILES πŸ“‚

  • <sge_root>/<cell>/common/act_qmaster β€” Grid Engine master host file 🏠.

πŸ‘€ SEE ALSO πŸ‘€

sge_intro(1), qrstat(1), qrsub(1), qsub(1), sge_qmaster(8), sge_execd(8).

go read them, i'm not joking, they're literally right there πŸ¦‹


See sge_intro(1) for a full statement of rights and permissions πŸ“œ.


mwah πŸ’‹ that's the page! this one's from SGE 8.1.3pre, dated 2011-05-20 β€” an absolute vintage queen, and honestly she still eats πŸ‘‘βœ¨