You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@helix.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/05/17 05:33:16 UTC

[jira] [Commented] (HELIX-97) Scheduler message summary does not contain individual message results

    [ https://issues.apache.org/jira/browse/HELIX-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660298#comment-13660298 ] 

Hudson commented on HELIX-97:
-----------------------------

Integrated in helix #721 (See [https://builds.apache.org/job/helix/721/])
    [HELIX-97]Scheduler message summary does not contain individual message (Revision 96cc674174ae7e401f54bef43c11c0bc0f02986b)

     Result = SUCCESS
lushi04 : 
Files : 
* helix-admin-webapp/src/main/java/org/apache/helix/webapp/resources/SchedulerTasksResource.java
* helix-core/src/test/java/org/apache/helix/integration/TestSchedulerMessage.java
* helix-core/src/main/java/org/apache/helix/manager/zk/DefaultSchedulerMessageHandlerFactory.java

                
> Scheduler message summary does not contain individual message results
> ---------------------------------------------------------------------
>
>                 Key: HELIX-97
>                 URL: https://issues.apache.org/jira/browse/HELIX-97
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Shi Lu
>            Assignee: Shi Lu
>            Priority: Blocker
>
> Currently the scheduler message sent to controller will add scheduler task partitions to the scheduler task queue, and the offline->completed state transition will invoke the MessageHandler inside. The controller will check the external view of the scheduler tasks resource and update the controller scheduler message status updates. However the individual message result are not put back.
> Short term solution : Propose to put the individual task result in resource config, and is moved to controller status update, and then cleaned up by the controller. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira