-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allowing programmatic downloads in jupyterlab #27
Comments
Thanks for reporting @jorana. I can reproduce the error for that run, but I'm not sure what's causing it. Seems to be something with CCIN2P3, as the same command for a run on UC_OSG_USERDISK works fine:
|
Thanks Evan for checking it out. I will try again for more runs next time, but I thought I was seeing it for a whole set of runs. It then seemed to work fine on the login node. |
Hi, I have also reproduced this issue (with run 8000 since this run has both copies). With this command:
the download is immediate, while with this command:
it took several hours (about 4), but then it does it. The output is the following:
My (temporary) conclusion is that all these tests have been done during a massive data transfer from CCIN2P3 to UC (started on April 21 morning) and this transfer had some impact on the speed performances. I will redo this test as soon as this massive data transfer is completed, to check that in normal condition it works. |
Software
Description
It would be nice if we could admix download using jupyter bash magic such that one does not have to go do this manually on the login node. E.g. the command below. I am not sure if this is due to some setup in rucio/the container/.. or due to the fact that the batch nodes don't have internet access.
What I Did
!admix-download 012233 raw_records --threads 10 --dir /dali/lgrandi/angevaare/download_rr/.
Then, it simply hangs on this, and nothing really happens for hours. Running the exact command on the login node solves the issue but is not suitable since we don't want everyone to start doing jobs on the login node.
The text was updated successfully, but these errors were encountered: