You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2008/12/10 04:14:44 UTC

[jira] Created: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Enable JobTracker Instrumentation API with user job configuration
-----------------------------------------------------------------

                 Key: HADOOP-4818
                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
             Project: Hadoop Core
          Issue Type: Bug
          Components: mapred
         Environment: Redhat EL 5, Java 6
            Reporter: Eric Yang
             Fix For: 0.20.0


The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., if Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated HADOOP-4818:
------------------------------

    Attachment: HADOOP-4818.patch

- Make JobInstrumentation API public
- Send user job configuration to instrumentation API

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4818.patch
>
>
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., if Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated HADOOP-4818:
------------------------------

    Description: The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.  (was: The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., if Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.)

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4818.patch
>
>
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657657#action_12657657 ] 

Ari Rabkin commented on HADOOP-4818:
------------------------------------

Can you comment on why we don't want the API to be public?  Seems like that's very limiting...

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4818-1.patch, HADOOP-4818.patch
>
>
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658143#action_12658143 ] 

Eric Yang commented on HADOOP-4818:
-----------------------------------

Owen and Arun thinks it is too open for outside of hadoop community to inject code at this level.

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4818-1.patch, HADOOP-4818.patch
>
>
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated HADOOP-4818:
------------------------------

    Attachment: HADOOP-4818-1.patch

Discussion with Owen and Arun, and we don't want to make this API public.  Fix job conf parameter only.

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4818-1.patch, HADOOP-4818.patch
>
>
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655093#action_12655093 ] 

Ari Rabkin commented on HADOOP-4818:
------------------------------------

This appears both useful and correct.  +1

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4818.patch
>
>
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., if Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas updated HADOOP-4818:
----------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I committed this. Thanks, Eric

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4818-1.patch, HADOOP-4818.patch
>
>
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated HADOOP-4818:
------------------------------

        Assignee: Eric Yang
    Release Note: 
What is new in HADOOP-4818:

- Make Job Instrumentation API public
- Pass user job configuration to instrumentation API
          Status: Patch Available  (was: Open)

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4818.patch
>
>
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., if Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655879#action_12655879 ] 

Hadoop QA commented on HADOOP-4818:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12395711/HADOOP-4818.patch
  against trunk revision 725862.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no tests are needed for this patch.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 Eclipse classpath. The patch retains Eclipse classpath integrity.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3714/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3714/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3714/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3714/console

This message is automatically generated.

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4818.patch
>
>
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration

Posted by "Robert Chansler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Chansler updated HADOOP-4818:
------------------------------------

    Release Note:   (was: What is new in HADOOP-4818:

- Make Job Instrumentation API public
- Pass user job configuration to instrumentation API)

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4818-1.patch, HADOOP-4818.patch
>
>
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf, JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain job related configuration.  i.e., Chukwa could use this API to find out the job history file location.  In addition, the API should be public for general public to implement useful utilities to interface with this API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.