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

Boyang Jerry Peng updated STORM-1507:
-------------------------------------
    Description: When the parallelism of a component in a topology is changed, 
the thrift APIs to get the parallelism ("get_parallelism_hint()") of components 
still return the original parallelism of the component and not the parallelism 
it changed to.  This due to the fact that the thrift object responsible for 
holding the information about a component only gets initialized once in 
nimbus.clj but never gets updated when a change in parallelism happens.  This 
may also cause the UI to not display the correct parallelism as well.  (was: 
When the parallelism of a component in a topology is changed, the thrift APIs 
to get the parallelism ("get_parallelism_hint()") of components still return 
the original parallelism of the component and not the parallelism it changed 
to.  This due to the fact that the thrift object responsible for holding the 
information about a component only gets initialized once in nimbus.clj but 
never gets updated when a change in parallelism happens)

> Getting the parallelism of components via thrift API after a rebalance/change 
> in parallelism is incorrect
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: STORM-1507
>                 URL: https://issues.apache.org/jira/browse/STORM-1507
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Boyang Jerry Peng
>
> When the parallelism of a component in a topology is changed, the thrift APIs 
> to get the parallelism ("get_parallelism_hint()") of components still return 
> the original parallelism of the component and not the parallelism it changed 
> to.  This due to the fact that the thrift object responsible for holding the 
> information about a component only gets initialized once in nimbus.clj but 
> never gets updated when a change in parallelism happens.  This may also cause 
> the UI to not display the correct parallelism as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to