Open swarbred opened 2 years ago
2nd issue above resolved by increasing (in the cromwell conf) to
connectionTimeout = 360000
changed to
services {
MetadataService {
metadata-read-row-number-safety-threshold = 4000000
}
}
to hopefully resolve the original issue
My error not resolved :-( (looking at the wrong run)
Hopefully corrected
services {
MetadataService {
config {
metadata-read-row-number-safety-threshold = 4000000
}
}
}
@ljyanesm sorry to bother you the wheat run failed with
From a quick google this seems to relate to
https://github.com/broadinstitute/cromwell/blob/5f48ded459574c059a1ddbedb9b7df248da85052/cromwell.example.backends/cromwell.examples.conf#L519
I did have a go at updating the cromwell_noserver_slurm.conf and this errored, i may not have had the updated config correctly (if you could indicate specifically what needs to be added that would be helpful) but the error on the rerun is not to do with this anyway as rerunning with the unchanged cromwell_noserver_slurm.conf also gives the error below
I assume this relates to cromwell not sutting down correctly and the connection perhaps still being open, any way to resolve this (the wheat run had completed all the main steps when the above error was raised, so I would prefer not to have to rerun everything).
Error on restarting with original config