helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shi Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HELIX-97) Scheduler message summary does not contain individual message results
Date Fri, 17 May 2013 17:27:16 GMT

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

Shi Lu commented on HELIX-97:
-----------------------------

Shorterm solution is to provide capability to fall-back to old way

Long term solution is to integrate with customizable task-result / partition metadata stores
                
> 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: Critical
>
> 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

Mime
View raw message