-
Notifications
You must be signed in to change notification settings - Fork 159
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
respiting of a subjoin always fails #2372
Comments
This works fine for me - it looks like you have doing something odd to your job repository. raise RepositoryError("Subjob key %s is already in the subjob XML cache!" % k) |
I've double checked it: with ganga version 8.6.10 it works as expected ... |
Ganga In [6]: jobs(31).subjobs(683).resplit(SplitByFiles( filesPerJob = 1 )) [13:06:31] |
So we fixed the error in the exception raising - maybe you could try again with the DEV version? |
Thanks for the fix and sorry for the late reply. I cannot test exactly the same subjob, because this subjoin is in a state which does not allow resplitting: For another subjob of the same job the respiting is in progress for about 30min right now. This is possibly another issue of the ganga 8.7.X versions ... for large amount of jobs, subjoins all 8.7.X versions I've used the processing times for commands are incredibly slow ... since I will stop working now I keep the ganga session open and will report back what will have happened ... |
Still by now the command to resplit is stuck: My provider will change IP address of my home router soon and will stop my lxplus session ... |
What do you mean? How exactly have you managed to produce this? Have you had a look at what the debug say. We need more information otherwise we cannot help. It works fine for me, so there must be something particular about your setup. |
I have a lot of jobs in my session and I am trying to be very careful when e.g. ending a ganga session. Using the newer ganga version for the amount of jobs I am processing takes me a lot of patience, because ganga is very, very slow. I cannot remove the ganga session output, because I need it to be able to find out the URLs of the data at the storage elements. So I've used ganga on a different cluster than lxplus to have a more reactive session ... perhaps it would be good to develop some sort of stress test using a lot of jobs for testing new ganga versions ...? |
I use Ganga myself to submit many thousands of jobs for my own analyses and have had no issues. We work very hard to test it and make it faster - in fact the upgrade from 8.6.9 -> 8.7.0 brought significant speed increases. Could you start Ganga in debug mode, try to resplit and send the output? |
I have started ganga in debug more. Here are the results and sorry for the delay. 1.) ganga start takes long. A while ganga was stuck during the startup here is the printout I saw:
Proxies uploaded: |
Dear developers! Using the latest released ganga version 8.7.8 a respiting of a job always fails. Earlier versions did not have this issue. Could you please have a look? Thx!
The text was updated successfully, but these errors were encountered: