You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it is a good idea to merge storm-yarn into storm source tree. This approach have been adopted by spark. spark-yarn is a internal part of spark.
Advantages:
More easy to manage the dependance.
We can finally throw away the zmq code and dependance for build and test.
In storm-yarn, we don't need to install both, don't need to manage STORM_HOME in storm-yarn anymore. There will be single installation, and this can be build into single rpm package. Very convenient for management.
No longer need local storm.zip package. We can set the jars(storm.jar storm-yarn.jar) and libraries as local resources, and use this to start container on another machine.
Steps:
First need to change the groupId to "storm"
Better we need to use pom to manage storm, so that we can more easily aggregate storm-yarn as a module.
Add interface in storm-yarn scripts, so that we can submit storm job with storm-yarn script file directly (no need to getStormConfig)
We should not try to copy storm.zip into HDFS and use that zip to deploy. Instead, we can just add lib and jars into local resource. Otherwise, there are two copy of storm. One is in STORM_HOME, the other is in storm.zip.
The text was updated successfully, but these errors were encountered:
Totally agree. Storm has a proposal up to become an Apache incubator project. The plan was to wait until it is part of the incubator and then work with Nathan about brining in it.
I think it is a good idea to merge storm-yarn into storm source tree. This approach have been adopted by spark. spark-yarn is a internal part of spark.
Advantages:
Steps:
The text was updated successfully, but these errors were encountered: