<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">So here is an update on the progress of the mosaswift test scripts:<div>I have a working CDM script and catsn(well semi working). The issue was that the rule for CDM direct was matching "data_files" and using an absolute path with "data_files" at the end. This caused the path to look like /path/to/data_files/data_files since CDM takes what it matched and appends it to the absolute path that was provided. This will documented better in the CDM section of the user guide. The other error that was brought to light was that the worker nodes do not share /tmp so they couldn't find error files when checking to see if they jobs completed. This was resolved by setting the number of workers from 1 to 2. Once mosastore is set up on the worker nodes this number can vary since all the workers will share /tmp/mosa(at least that is my assumption).</div><div><br></div><div>I say semi working because I intended the script to build up output during the stages on the swift run and the final output would show that it was stored temporarily in /tmp. This is not happening as the final output for the file contains only the last line(a Hello from <id> line). I believe this is due to how CDM using symlinks for the files that is matched, so a symlink is being overwritten instead of at the file it points to. I ran into this problem in the past(but this is documented in the user guide) and just need verify that this is indeed the issue.</div><div><br></div><div>I have also fixed the parameter issue so we get a better error message for the problem. It provides a bit better error message as to what the issue was.</div><div><br></div><div><div><div>On Mar 13, 2012, at 1:02 PM, Emalayan Vairavanathan wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Hi Jon,</span></div><div><br><span></span></div><div><span>Great news and thank you for the update. I think we are getting very closer. Please let me know if I can help you.</span></div><div><br><span></span></div><div><span>I am cc-ing MosaStore group to inform about the progress.</span></div><div><br><span></span></div><div><span>Thank you</span></div><div><span>Emalayan<br></span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Jonathan Monette <<a href="mailto:jonmon@mcs.anl.gov">jonmon@mcs.anl.gov</a>><br> <b><span style="font-weight: bold;">To:</span></b> "<a href="mailto:svemalayan@yahoo.com">svemalayan@yahoo.com</a>"
<<a href="mailto:svemalayan@yahoo.com">svemalayan@yahoo.com</a>> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, 13 March 2012 10:03 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Mosaswift update<br> </font> </div> <br>Emalayan,<br> I may have figured out how to use the intermediate file set up that moss needs. We will need to use something called provider staging which is a feature Swift has. Provider staging copies data directly to the compute node. I will experiment with this and see if this is the missing piece we need. <br><br> </div> </div> </div></div></blockquote></div><br></div></body></html>