Is LSF queue allowed to preempt itself?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1














I have an LSF queue, say it's queue A. I only want higher priority jobs in queue A to preempt lower priority jobs in queue A, but not jobs in any other queues. If I set queue A to be preemptable, could I set it to be preemptable only by itself (queue A)? Or if this is not allowed, what could achieve my goal?










share|improve this question























  • Your question is perhaps on-topic, if you're using en.wikipedia.org/wiki/Platform_LSF on a UNIX system of some sort; are you?
    – Jeff Schaller
    Dec 27 '18 at 16:06















1














I have an LSF queue, say it's queue A. I only want higher priority jobs in queue A to preempt lower priority jobs in queue A, but not jobs in any other queues. If I set queue A to be preemptable, could I set it to be preemptable only by itself (queue A)? Or if this is not allowed, what could achieve my goal?










share|improve this question























  • Your question is perhaps on-topic, if you're using en.wikipedia.org/wiki/Platform_LSF on a UNIX system of some sort; are you?
    – Jeff Schaller
    Dec 27 '18 at 16:06













1












1








1







I have an LSF queue, say it's queue A. I only want higher priority jobs in queue A to preempt lower priority jobs in queue A, but not jobs in any other queues. If I set queue A to be preemptable, could I set it to be preemptable only by itself (queue A)? Or if this is not allowed, what could achieve my goal?










share|improve this question















I have an LSF queue, say it's queue A. I only want higher priority jobs in queue A to preempt lower priority jobs in queue A, but not jobs in any other queues. If I set queue A to be preemptable, could I set it to be preemptable only by itself (queue A)? Or if this is not allowed, what could achieve my goal?







high-performance platform-lsf






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 27 '18 at 3:37









Rui F Ribeiro

39.3k1479131




39.3k1479131










asked Dec 27 '18 at 3:34









PengPeng

61




61











  • Your question is perhaps on-topic, if you're using en.wikipedia.org/wiki/Platform_LSF on a UNIX system of some sort; are you?
    – Jeff Schaller
    Dec 27 '18 at 16:06
















  • Your question is perhaps on-topic, if you're using en.wikipedia.org/wiki/Platform_LSF on a UNIX system of some sort; are you?
    – Jeff Schaller
    Dec 27 '18 at 16:06















Your question is perhaps on-topic, if you're using en.wikipedia.org/wiki/Platform_LSF on a UNIX system of some sort; are you?
– Jeff Schaller
Dec 27 '18 at 16:06




Your question is perhaps on-topic, if you're using en.wikipedia.org/wiki/Platform_LSF on a UNIX system of some sort; are you?
– Jeff Schaller
Dec 27 '18 at 16:06










1 Answer
1






active

oldest

votes


















0














LSF support 2 modes of preemption: Queue based and license based. In your case, since the queue priority of your two jobs is the same (both are in the same queue) preemption won't be triggered.



If your two jobs are part of different license scheduler projects, and the running job is borrowing a license from the project of the pending job, then preemption can happen. But from your description I'm guessing that this isn't the case.



Unfortunately preemption based on (for example) job priority or fairshare weight is not supported.






share|improve this answer
















  • 1




    Thanks. Yeah it looks like LSF only supports preemption based on queue priority, instead of job priority. I'd have to use 2 queues with different priorities maybe.
    – Peng
    Dec 28 '18 at 0:12










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491065%2fis-lsf-queue-allowed-to-preempt-itself%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














LSF support 2 modes of preemption: Queue based and license based. In your case, since the queue priority of your two jobs is the same (both are in the same queue) preemption won't be triggered.



If your two jobs are part of different license scheduler projects, and the running job is borrowing a license from the project of the pending job, then preemption can happen. But from your description I'm guessing that this isn't the case.



Unfortunately preemption based on (for example) job priority or fairshare weight is not supported.






share|improve this answer
















  • 1




    Thanks. Yeah it looks like LSF only supports preemption based on queue priority, instead of job priority. I'd have to use 2 queues with different priorities maybe.
    – Peng
    Dec 28 '18 at 0:12















0














LSF support 2 modes of preemption: Queue based and license based. In your case, since the queue priority of your two jobs is the same (both are in the same queue) preemption won't be triggered.



If your two jobs are part of different license scheduler projects, and the running job is borrowing a license from the project of the pending job, then preemption can happen. But from your description I'm guessing that this isn't the case.



Unfortunately preemption based on (for example) job priority or fairshare weight is not supported.






share|improve this answer
















  • 1




    Thanks. Yeah it looks like LSF only supports preemption based on queue priority, instead of job priority. I'd have to use 2 queues with different priorities maybe.
    – Peng
    Dec 28 '18 at 0:12













0












0








0






LSF support 2 modes of preemption: Queue based and license based. In your case, since the queue priority of your two jobs is the same (both are in the same queue) preemption won't be triggered.



If your two jobs are part of different license scheduler projects, and the running job is borrowing a license from the project of the pending job, then preemption can happen. But from your description I'm guessing that this isn't the case.



Unfortunately preemption based on (for example) job priority or fairshare weight is not supported.






share|improve this answer












LSF support 2 modes of preemption: Queue based and license based. In your case, since the queue priority of your two jobs is the same (both are in the same queue) preemption won't be triggered.



If your two jobs are part of different license scheduler projects, and the running job is borrowing a license from the project of the pending job, then preemption can happen. But from your description I'm guessing that this isn't the case.



Unfortunately preemption based on (for example) job priority or fairshare weight is not supported.







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 27 '18 at 23:00









Michael ClossonMichael Closson

1513




1513







  • 1




    Thanks. Yeah it looks like LSF only supports preemption based on queue priority, instead of job priority. I'd have to use 2 queues with different priorities maybe.
    – Peng
    Dec 28 '18 at 0:12












  • 1




    Thanks. Yeah it looks like LSF only supports preemption based on queue priority, instead of job priority. I'd have to use 2 queues with different priorities maybe.
    – Peng
    Dec 28 '18 at 0:12







1




1




Thanks. Yeah it looks like LSF only supports preemption based on queue priority, instead of job priority. I'd have to use 2 queues with different priorities maybe.
– Peng
Dec 28 '18 at 0:12




Thanks. Yeah it looks like LSF only supports preemption based on queue priority, instead of job priority. I'd have to use 2 queues with different priorities maybe.
– Peng
Dec 28 '18 at 0:12

















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491065%2fis-lsf-queue-allowed-to-preempt-itself%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)