helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kanak Biscuitwala (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HELIX-481) Update cluster cache when the provisioning stage updates configs
Date Tue, 29 Jul 2014 00:39:38 GMT

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

Kanak Biscuitwala updated HELIX-481:
------------------------------------

    Description: 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.
 (was: If containers fail, we should ensure that the target provider is still capable of doing
the right thing and requesting for a replacement in the fixed target case.

We can test this via shutdown messages and the update container config tools that already
exist.)

> 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
>
> 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)

Mime
View raw message