-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major
-
Affects Version/s: master, 5.0.8
-
Component/s: Planner: Glite/Blahp
-
None
-
Environment:submitting to a local SGE cluster
https://pegasus.isi.edu/documentation/user-guide/deployment-scenarios.html#setting-job-requirements
when submitting to a local SGE cluster using the Glite style, the pegasus profile memory is translated to it's numeric value in MB by the workflow API . This value is then passed on, and set in remote_ce_requirements classad for the job from where it is picked up by the blahp layer in the sge_local_submit_attributes.sh file.
However, SGE for it's memory parameters (h_vmem etc) always requires a suffix (G for GB , M for MB) to be associated