[jira] Updated: (MAPREDUCE-1027) jobtracker.jsp can have an html text block for announcements by admins.

2009-11-07 Thread Amar Kamat (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amar Kamat updated MAPREDUCE-1027:
--

Attachment: mapred-1027-v1.4.patch

Attaching a new patch with a testcase. The announcement file is passed using  
_mapreduce.jobtracker.announcements.location_. One message/announcement is one 
line in announcement file. Total number of announcements can be controlled by 
_mapreduce.jobtracker.announcements.maxsize_. Example announcement file
{noformat}
*new*This is another announcement
This is the first announcement
{noformat}
Hint : Add a *new* keyword for new announcements. Also the announcements can 
have html tags.

Result of test-patch
[exec] +1 overall.  
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 8 new or 
modified tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.

Testing in progress.

> jobtracker.jsp can have an html text block for announcements by admins.
> ---
>
> Key: MAPREDUCE-1027
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1027
> Project: Hadoop Map/Reduce
>  Issue Type: Improvement
>  Components: jobtracker
>Reporter: Vinod K V
> Attachments: mapred-1027-v1.2.patch, mapred-1027-v1.4.patch
>
>
> jobtracker.jsp is the first page for users of Map/Reduce clusters and can be 
> used for sending information across to all users. It will be useful to have a 
> text block on this page where administrators can put any latest 
> notices/announcements time to time.

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



[jira] Commented: (MAPREDUCE-707) Provide a jobconf property for explicitly assigning a job to a pool

2009-11-07 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774632#action_12774632
 ] 

Hudson commented on MAPREDUCE-707:
--

Integrated in Hadoop-Mapreduce-trunk #136 (See 
[http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/136/])


> Provide a jobconf property for explicitly assigning a job to a pool
> ---
>
> Key: MAPREDUCE-707
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-707
> Project: Hadoop Map/Reduce
>  Issue Type: New Feature
>  Components: contrib/fair-share
>Reporter: Matei Zaharia
>Assignee: Alan Heirich
>Priority: Trivial
> Fix For: 0.22.0
>
> Attachments: MAPREDUCE-707-1-apache.patch, 
> MAPREDUCE-707-2-apache.patch, MAPREDUCE-707-apache.patch
>
>
> A common use case of the fair scheduler is to have one pool per user, but 
> then to define some special pools for various production jobs, import jobs, 
> etc. Therefore, it would be nice if jobs went by default to the pool of the 
> user who submitted them, but there was a setting to explicitly place a job in 
> another pool. Today, this can be achieved through a sort of trick in the 
> JobConf:
> {code}
> 
>   mapred.fairscheduler.poolnameproperty
>   pool.name
> 
> 
>   pool.name
>   ${user.name}
> 
> {code}
> This JIRA proposes to add a property called mapred.fairscheduler.pool that 
> allows a job to be placed directly into a pool, avoiding the need for this 
> trick.

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



[jira] Commented: (MAPREDUCE-1177) TestTaskTrackerMemoryManager retries a task for more than 100 times.

2009-11-07 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774633#action_12774633
 ] 

Hudson commented on MAPREDUCE-1177:
---

Integrated in Hadoop-Mapreduce-trunk #136 (See 
[http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/136/])


> TestTaskTrackerMemoryManager retries a task for more than 100 times.
> 
>
> Key: MAPREDUCE-1177
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1177
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: tasktracker, test
>Affects Versions: 0.21.0, 0.22.0
>Reporter: Amareshwari Sriramadasu
>Assignee: Vinod K V
>Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1177-20091102.txt, 
> TEST-org.apache.hadoop.mapred.TestTaskTrackerMemoryManager.txt
>
>
> TestTaskTrackerMemoryManager retries a task for more than 100 times.
> The logs showing the same:
> {noformat}
> 2009-11-02 12:41:20,489 INFO  mapred.JobInProgress 
> (JobInProgress.java:completedTask(2530)) - Task 
> 'attempt_20091102123356106_0001_m_02_145' has completed 
> task_20091102123356106_0001_m_02 successfully.
> {noformat}
> Sometimes the test timesout also.

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



[jira] Commented: (MAPREDUCE-1147) Map output records counter missing for map-only jobs in new API

2009-11-07 Thread Amar Kamat (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774584#action_12774584
 ] 

Amar Kamat commented on MAPREDUCE-1147:
---

TestGridmixSubmission fails intermittently.

> Map output records counter missing for map-only jobs in new API
> ---
>
> Key: MAPREDUCE-1147
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1147
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>Affects Versions: 0.20.1, 0.21.0
>Reporter: Chris Douglas
>Assignee: Amar Kamat
>Priority: Blocker
> Fix For: 0.20.2
>
> Attachments: mapred-1147-v1.3.patch
>
>
> In the new API, the counter for map output records is not incremented for 
> map-only jobs

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