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

ASF GitHub Bot commented on HELIX-709:
--------------------------------------

GitHub user zhan849 opened a pull request:

    https://github.com/apache/helix/pull/208

    [HELIX-709] Prepare controller stages for async execution

    - Implemented AbstractAsyncBaseStage
    - Refactored TEVCalcState and PersistAssignmentStage to use 
AbstractAsyncBaseStage

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zhan849/helix harry/aabs

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/helix/pull/208.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #208
    
----
commit 9080c64429d724aa959207411ca06d690f5ee840
Author: Harry Zhang <hrzhang@...>
Date:   2018-06-28T21:25:21Z

    [HELIX-709] Prepare controller stages for async execution

----


> Prepare controller stages for async execution
> ---------------------------------------------
>
>                 Key: HELIX-709
>                 URL: https://issues.apache.org/jira/browse/HELIX-709
>             Project: Apache Helix
>          Issue Type: Task
>            Reporter: Hao Zhang
>            Priority: Major
>
> There are a couple of stages in helix controller that can be executed 
> asynchronously, but each execution should be done in order. Currently for 
> helix controller, we have a thread pool for un-ordered execution, but we also 
> need one for ordered execution.
> In this ticket should do the following:
> 1. Create a pool of configurable workers using DedupEventProcessor
> 2. Create AbstractAsyncBaseStage for those stages that can be executed 
> asynchronously to share common code
> AC:
> Create AbstractAsyncBaseStage and DedupFIFOWorkerPool for async execution, 
> pass all tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to