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 2014/07/30 21:20:41 UTC

[jira] [Commented] (HELIX-481) Update cluster cache when the provisioning stage updates configs

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

Hudson commented on HELIX-481:
------------------------------

SUCCESS: Integrated in helix #1272 (See [https://builds.apache.org/job/helix/1272/])
[HELIX-481] Keep controller cache in sync with container updates (kanak: rev 08371b561353c0b93fb6931f69d3ed01dbb634de)
* helix-provisioning/src/main/java/org/apache/helix/provisioning/yarn/YarnProvisioner.java
* helix-core/src/main/java/org/apache/helix/controller/stages/ContainerProvisioningStage.java


> Update cluster cache when the provisioning stage updates configs
> ----------------------------------------------------------------
>
>                 Key: HELIX-481
>                 URL: https://issues.apache.org/jira/browse/HELIX-481
>             Project: Apache Helix
>          Issue Type: Sub-task
>            Reporter: Kanak Biscuitwala
>            Assignee: Kanak Biscuitwala
>
> When the ContainerProvisioningStage updates the state of its instances, it doesn't take into account the fact that the cache may not yet be refreshed to take this change into account for the next pipeline run. Thus, the update should be forced into the cache.



--
This message was sent by Atlassian JIRA
(v6.2#6252)