Dask with HTCondor scheduler





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















Background



I have an image analysis pipeline with parallelised steps. The pipeline is in python and the parallelisation is controlled by dask.distributed. The minimum processing set up has 1 scheduler + 3 workers with 15 processes each. In the first short step of the analysis I use 1 process/worker but all RAM of the node then in all other analysis steps all nodes and processes are used.



Issue



The admin will install HTCondor as a scheduler for the cluster.



Thought



In order order to have my code running on the new setup I was planning to use the approach showed in the dask manual for SGE because the cluster has a shared network files system.



# job1 
# Start a dask-scheduler somewhere and write connection information to file
qsub -b y /path/to/dask-scheduler --scheduler-file /path/to/scheduler.json

# Job2
# Start 100 dask-worker processes in an array job pointing to the same file
qsub -b y -t 1-100 /path/to/dask-worker --scheduler-file /path/to/scheduler.json

# Job3
# Start a process with the python code where the client is started this way
client = Client(scheduler_file='/path/to/scheduler.json')


Question and advice



If I understood correctly with this approach I will start scheduler, workers and analysis as independent jobs (different HTCondor submit files). How can I make sure that the order of execution will be correct? Is there a way I can use the same processing approach I have being using before or will be more efficient to translate the code to work better with HTCondor?
Thanks for the help!










share|improve this question























  • Are you aware of github.com/dask/dask-jobqueue ?

    – mdurant
    Nov 26 '18 at 20:50











  • Thanks!. Just saw it! but no HTCondor support yet. github.com/dask/dask-jobqueue/issues/100

    – s1mc0d3
    Nov 27 '18 at 7:14











  • Please comment on the thread expressing your interest. Perhaps you can help test. That would be better than trying to come up with a custom script of your own.

    – mdurant
    Nov 27 '18 at 14:33











  • I will add a comment in the opened issue!

    – s1mc0d3
    Dec 3 '18 at 12:17


















0















Background



I have an image analysis pipeline with parallelised steps. The pipeline is in python and the parallelisation is controlled by dask.distributed. The minimum processing set up has 1 scheduler + 3 workers with 15 processes each. In the first short step of the analysis I use 1 process/worker but all RAM of the node then in all other analysis steps all nodes and processes are used.



Issue



The admin will install HTCondor as a scheduler for the cluster.



Thought



In order order to have my code running on the new setup I was planning to use the approach showed in the dask manual for SGE because the cluster has a shared network files system.



# job1 
# Start a dask-scheduler somewhere and write connection information to file
qsub -b y /path/to/dask-scheduler --scheduler-file /path/to/scheduler.json

# Job2
# Start 100 dask-worker processes in an array job pointing to the same file
qsub -b y -t 1-100 /path/to/dask-worker --scheduler-file /path/to/scheduler.json

# Job3
# Start a process with the python code where the client is started this way
client = Client(scheduler_file='/path/to/scheduler.json')


Question and advice



If I understood correctly with this approach I will start scheduler, workers and analysis as independent jobs (different HTCondor submit files). How can I make sure that the order of execution will be correct? Is there a way I can use the same processing approach I have being using before or will be more efficient to translate the code to work better with HTCondor?
Thanks for the help!










share|improve this question























  • Are you aware of github.com/dask/dask-jobqueue ?

    – mdurant
    Nov 26 '18 at 20:50











  • Thanks!. Just saw it! but no HTCondor support yet. github.com/dask/dask-jobqueue/issues/100

    – s1mc0d3
    Nov 27 '18 at 7:14











  • Please comment on the thread expressing your interest. Perhaps you can help test. That would be better than trying to come up with a custom script of your own.

    – mdurant
    Nov 27 '18 at 14:33











  • I will add a comment in the opened issue!

    – s1mc0d3
    Dec 3 '18 at 12:17














0












0








0








Background



I have an image analysis pipeline with parallelised steps. The pipeline is in python and the parallelisation is controlled by dask.distributed. The minimum processing set up has 1 scheduler + 3 workers with 15 processes each. In the first short step of the analysis I use 1 process/worker but all RAM of the node then in all other analysis steps all nodes and processes are used.



Issue



The admin will install HTCondor as a scheduler for the cluster.



Thought



In order order to have my code running on the new setup I was planning to use the approach showed in the dask manual for SGE because the cluster has a shared network files system.



# job1 
# Start a dask-scheduler somewhere and write connection information to file
qsub -b y /path/to/dask-scheduler --scheduler-file /path/to/scheduler.json

# Job2
# Start 100 dask-worker processes in an array job pointing to the same file
qsub -b y -t 1-100 /path/to/dask-worker --scheduler-file /path/to/scheduler.json

# Job3
# Start a process with the python code where the client is started this way
client = Client(scheduler_file='/path/to/scheduler.json')


Question and advice



If I understood correctly with this approach I will start scheduler, workers and analysis as independent jobs (different HTCondor submit files). How can I make sure that the order of execution will be correct? Is there a way I can use the same processing approach I have being using before or will be more efficient to translate the code to work better with HTCondor?
Thanks for the help!










share|improve this question














Background



I have an image analysis pipeline with parallelised steps. The pipeline is in python and the parallelisation is controlled by dask.distributed. The minimum processing set up has 1 scheduler + 3 workers with 15 processes each. In the first short step of the analysis I use 1 process/worker but all RAM of the node then in all other analysis steps all nodes and processes are used.



Issue



The admin will install HTCondor as a scheduler for the cluster.



Thought



In order order to have my code running on the new setup I was planning to use the approach showed in the dask manual for SGE because the cluster has a shared network files system.



# job1 
# Start a dask-scheduler somewhere and write connection information to file
qsub -b y /path/to/dask-scheduler --scheduler-file /path/to/scheduler.json

# Job2
# Start 100 dask-worker processes in an array job pointing to the same file
qsub -b y -t 1-100 /path/to/dask-worker --scheduler-file /path/to/scheduler.json

# Job3
# Start a process with the python code where the client is started this way
client = Client(scheduler_file='/path/to/scheduler.json')


Question and advice



If I understood correctly with this approach I will start scheduler, workers and analysis as independent jobs (different HTCondor submit files). How can I make sure that the order of execution will be correct? Is there a way I can use the same processing approach I have being using before or will be more efficient to translate the code to work better with HTCondor?
Thanks for the help!







python parallel-processing dask condor






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 26 '18 at 20:31









s1mc0d3s1mc0d3

10410




10410













  • Are you aware of github.com/dask/dask-jobqueue ?

    – mdurant
    Nov 26 '18 at 20:50











  • Thanks!. Just saw it! but no HTCondor support yet. github.com/dask/dask-jobqueue/issues/100

    – s1mc0d3
    Nov 27 '18 at 7:14











  • Please comment on the thread expressing your interest. Perhaps you can help test. That would be better than trying to come up with a custom script of your own.

    – mdurant
    Nov 27 '18 at 14:33











  • I will add a comment in the opened issue!

    – s1mc0d3
    Dec 3 '18 at 12:17



















  • Are you aware of github.com/dask/dask-jobqueue ?

    – mdurant
    Nov 26 '18 at 20:50











  • Thanks!. Just saw it! but no HTCondor support yet. github.com/dask/dask-jobqueue/issues/100

    – s1mc0d3
    Nov 27 '18 at 7:14











  • Please comment on the thread expressing your interest. Perhaps you can help test. That would be better than trying to come up with a custom script of your own.

    – mdurant
    Nov 27 '18 at 14:33











  • I will add a comment in the opened issue!

    – s1mc0d3
    Dec 3 '18 at 12:17

















Are you aware of github.com/dask/dask-jobqueue ?

– mdurant
Nov 26 '18 at 20:50





Are you aware of github.com/dask/dask-jobqueue ?

– mdurant
Nov 26 '18 at 20:50













Thanks!. Just saw it! but no HTCondor support yet. github.com/dask/dask-jobqueue/issues/100

– s1mc0d3
Nov 27 '18 at 7:14





Thanks!. Just saw it! but no HTCondor support yet. github.com/dask/dask-jobqueue/issues/100

– s1mc0d3
Nov 27 '18 at 7:14













Please comment on the thread expressing your interest. Perhaps you can help test. That would be better than trying to come up with a custom script of your own.

– mdurant
Nov 27 '18 at 14:33





Please comment on the thread expressing your interest. Perhaps you can help test. That would be better than trying to come up with a custom script of your own.

– mdurant
Nov 27 '18 at 14:33













I will add a comment in the opened issue!

– s1mc0d3
Dec 3 '18 at 12:17





I will add a comment in the opened issue!

– s1mc0d3
Dec 3 '18 at 12:17












0






active

oldest

votes












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f53488603%2fdask-with-htcondor-scheduler%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • 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%2fstackoverflow.com%2fquestions%2f53488603%2fdask-with-htcondor-scheduler%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

Wiesbaden

Marschland

Dieringhausen