Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Submitting a topology to storm cluster - Required field 'nimbus_uptime_secs' is unset!

avatar
New Contributor

Hi, I'm trying to submit a topology on storm cluster using StormSubmitter , however I got the following error: [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:java (default-cli) on project realtime_piplines: An exception occured while executing the Java class. null: InvocationTargetException: org.apache.thrift7.protocol.TProtocolException: Required field 'nimbus_uptime_secs' is unset! I am running HDP 2.3.4 with Storm version '0.10.0' on RHEL 6.5.

Thanks in advance,

1 ACCEPTED SOLUTION

avatar

@Yuri Chemolosov @Artem Ervits one of the workarounds I think of is to make storm-0.11-SNAPSHOT as dependency at the client side for the topology and use the StormSubmitter for 0.11-SNAPSHOT version.

add the following repository in your pom.xml https://repository.apache.org/content/repositories/snapshots/ to get the latest snapshot for storm.

View solution in original post

12 REPLIES 12

avatar
Master Mentor

@Hani Al-Shater can you paste the command you use to execute the topology and paste the supervisor logs?

avatar
Explorer

I am experiencing the same issue with freshly installed HDP 2.3 cluster.

I guess, it has been fixed in Storm re: https://issues.apache.org/jira/browse/STORM-1189 but only available in ver. 0.11.0

What would be the best way get my topology submitted to storm ? I there a nice way to patch or downgrade/upgrade the system?

I use steamparse to submit the topology to the Storm.

avatar
Master Mentor

@Yuri Chemolosov @schintalapani

good find Yuri, have you tried the suggested work around and set nimbus_uptime_secs to 0?

the https://storm.apache.org/apidocs/backtype/storm/generated/ClusterSummary.html#set_nimbus_uptime_secs...

let me know if the workaround works, I see it is happening frequently.

avatar
Explorer

I have used 0.11.0-SNAPSHOT storm-core to submit the task as suggested. It acutaly passes the submission phase (no more original error). The topology get deployed to the cluster. But then it fails to start with some incompatibility exception on the server side.

Is there a way to selectively upgrade servers side Storm to the snapshot version?

avatar
Master Mentor

@Yuri Chemolosov there's no way to upgrade individual components aside from Spark.

avatar

@Yuri Chemolosov @Artem Ervits one of the workarounds I think of is to make storm-0.11-SNAPSHOT as dependency at the client side for the topology and use the StormSubmitter for 0.11-SNAPSHOT version.

add the following repository in your pom.xml https://repository.apache.org/content/repositories/snapshots/ to get the latest snapshot for storm.

avatar
Master Mentor

@Hani Al-Shater try this and let us know

avatar
Explorer

Tried everything exhausting the options. Nothing worked, neither new client, nor old. Locally rebuilt patched storm-core did not work either.

Had to reinstall the whole cluster thing downgrading to HDP 2.2, moving to Ubuntu 12 from Debian 7, resolving all the failed dependency of the OS.

Now I am still getting the 'incompatibility error'

avatar
Master Mentor

@Yuri Chemolosov can you confirm storm-starter can work on your cluster compiled with the version of your HDP cluster?