locked
About NameSpace Information for job submission filter RRS feed

  • Question

  • Hi All,

    I find another weird thing about the job submission filter in HPCS2008.
    My job submission filter's input job file doesn't contain namespace information which is in the original job file.
    e.g.
    I submit job through command: job submit /jobfile:jt.xml.
    jt.xml file is:
    <?xml version="1.0" encoding="utf-8"?>  
    <Job xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Name="ExtendedTermsName" JobTemplate="Default" >  
      <Tasks xmlns="http://www.microsoft.com/ComputeCluster/">  
        <Task Id="1" Name="task1" MinCores="1" MaxCores="1" CommandLine="hostname.exe">  
           <EnvironmentVariables>  
           <Variable>  
              <Name>MDCE_DECODE_FUNCTION</Name>  
              <Value>decodeCcsSingleTask</Value>  
            </Variable>  
           </EnvironmentVariables>  
        </Task>  
      </Tasks>  
    </Job>  
    While what my job submission filter get is :
    <?xml version="1.0" encoding="utf-8"?>  
    <Job Id="6" IsBackfill="false" Name="ExtendedTermsName" Project="" SubmittedBy="TESTDOMAIN\Administrator" User="TESTDOMAIN\Administrator">  
      <Tasks>  
        <Task AllocatedNodes="" Id="6" CommandLine="hostname.exe" MaximumNumberOfProcessors="1" MinimumNumberOfProcessors="1" Name="task1" ParentJobId="6" State="Submitted">  
          <EnvironmentVariables>  
            <Variable>  
              <Name>MDCE_DECODE_FUNCTION</Name>  
              <Value>decodeCcsSingleTask</Value>  
            </Variable>  
          </EnvironmentVariables>  
        </Task>  
      </Tasks>  
    </Job>  
    You can find that all the namespace information of XML is missing.

    Without these information, Cluster::CreateJobFromXmlFile cannot parse job file currently! Do I have to parse job file by myself? :-(

    Is it a bug or not?
    Friday, September 26, 2008 3:33 AM

Answers

All replies

  • Woody,
    This is related to the bug that you posted earlier where we are missing some things in the Submission/Activation filter XML.  We are looking into that issue still as it may reuqire a product update to fix.  That being said . . . I'm not clear on why the namespace is causing a problem for you . . . why are you creating a new job based on the XML passed to the filter?

    The way we expect filters to be used it just like the sample filters that are posted in our help . . . namely that you will use some XML reading API to grok the file and find the terms that you are interseted in.  So if you're doing something else with them, it would be great for us to understand exactly what it is so we can figure out how to support it.

    Thanks,
    Josh
    -Josh
    Friday, September 26, 2008 8:28 PM
    Moderator
  • Hi Barndawgie,

    Yes, you are right, my way using filter is indeed a little strange. Because the scheduler doesn't support meta-schedule feature, so I have to use job submission filter to find out those jobs I want then re-assign them to some other clusters.

    Do you have any suggestion about this? Any help will be appreciated!

    Thanks,
    Woody
    • Edited by WoodyZhou Saturday, September 27, 2008 5:14 AM
    Saturday, September 27, 2008 5:13 AM
  • Oh, BTW, the namespace is of course not a problem for me. I just want to assure whether MS will change this or not in the future.
    So that I can make my filter fit that. :-)
    Saturday, September 27, 2008 5:20 AM
  • Just so you know you're not forgotten . . . we are still looking into this.  I hope to post some information soon.
    -Josh
    Friday, October 10, 2008 12:15 AM
    Moderator
  •  Hi,

    It looks like I  just had the same issue with a custom submission filter, I see this thread from last month, has there been any update?
     
    I had used the example as a starting point as well, but it appears this bug created me problems were it worked perfectly from the command line with a saved job file, but not when it was enabled and called from HPC Server. After seeing this thread, I worked around it by parsing the XML differently than the example as to not depend on the namespace and that is working as a workaround.

    Saturday, October 11, 2008 1:53 AM
  • We are working on a fix for this (and other XML issues) to be released in the next couple of weeks.  This may require some reworking of your filters but will hopefully fix a number of problems that we've seen.  There are two threads going on about this right now; I'll keep updating the other one as we make progress:
    http://social.microsoft.com/Forums/en-US/windowshpcsched/thread/c69c79e2-cc5f-4b2f-b294-a245d83cc220

    Thanks!
    Josh
    -Josh
    Wednesday, October 15, 2008 5:42 PM
    Moderator
  • Check out my post here for some more details:
    https://windowshpc.net/Blogs/jobscheduler/Lists/Posts/Post.aspx?ID=12
    -Josh
    Thursday, November 6, 2008 7:26 PM
    Moderator