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

Zhuo Liu edited comment on STORM-1189 at 11/8/15 9:59 PM:
----------------------------------------------------------

Hi Michael, are you doing a rolling-upgrade from 0.9 to 0.10?
It seems that the field "nimbus_uptime_secs" only exists in 0.9.x for 
ClusterSummary; in 0.11.0, this field no longer exists because we introduce 
multiple nimbuses in HA. 


was (Author: zhuoliu):
Hi Michael, are you doing a rolling-upgrade from 0.9 to 0.10?
It seems that the field "nimbus_uptime_secs" only exists in 0.9.x for 
ClusterSummary; in 0.10.0, this field no longer exists. 
It is also possible that not all your nimbus and supervisor nodes have fully 
upgraded to 0.10.

> client.getClusterInfo() fails with Required field 'nimbus_uptime_secs' is 
> unset!
> --------------------------------------------------------------------------------
>
>                 Key: STORM-1189
>                 URL: https://issues.apache.org/jira/browse/STORM-1189
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 0.10.0
>         Environment: CentOS 7, Hortonworks 2.3, Java API
>            Reporter: Michael Sonst
>
> Hi,
> we are about to upgrade our cluster from 0.9.1-incubating to 0.10.0. I'm 
> currently testing whether the functionality is still working with 0.10.0 in 
> VMs.
> On 0.10.0 the following throws the exception mentioned below:
> ...
> NimbusClient nimbusClient = NimbusClient.getConfiguredClient(readConfig);
> Client client = nimbusClient.getClient();
> ClusterSummary clusterInfo = client.getClusterInfo();
> Exception:
> org.apache.thrift7.protocol.TProtocolException: Required field 
> 'nimbus_uptime_secs' is unset! 
> Struct:ClusterSummary(supervisors:[SupervisorSummary(host:n3.t3k.siemens.com, 
> uptime_secs:24297, num_workers:4, num_used_workers:0, 
> supervisor_id:4a87f03b-ea91-4b12-8cb9-9f7e26703b26, 
> version:0.10.0.2.3.0.0-2557)], nimbus_uptime_secs:0, topologies:[])
>       at 
> backtype.storm.generated.ClusterSummary.validate(ClusterSummary.java:515)
>       at 
> backtype.storm.generated.ClusterSummary$ClusterSummaryStandardScheme.read(ClusterSummary.java:613)
>       at 
> backtype.storm.generated.ClusterSummary$ClusterSummaryStandardScheme.read(ClusterSummary.java:549)
>       at backtype.storm.generated.ClusterSummary.read(ClusterSummary.java:473)
>       at 
> backtype.storm.generated.Nimbus$getClusterInfo_result$getClusterInfo_resultStandardScheme.read(Nimbus.java:16546)
>       at 
> backtype.storm.generated.Nimbus$getClusterInfo_result$getClusterInfo_resultStandardScheme.read(Nimbus.java:16531)
>       at 
> backtype.storm.generated.Nimbus$getClusterInfo_result.read(Nimbus.java:16470)
>       at org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
>       at 
> backtype.storm.generated.Nimbus$Client.recv_getClusterInfo(Nimbus.java:569)
>       at 
> backtype.storm.generated.Nimbus$Client.getClusterInfo(Nimbus.java:557)
> Switching back to 0.9.1-incubating showed, that the code still works fine 
> there.
> BR Michael



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

Reply via email to