For versioning support you need to add the app_version property and use
the --version option when uploading different versions of an app-package
using (package --install). That should be it.

Refer to 
http://slider.incubator.apache.org/docs/slider_specs/application_pkg_upgrad
e.html for more help.

What issues are you facing when submitting topologies?

-Gour

On 6/15/15, 2:41 AM, "Chackravarthy Esakkimuthu" <[email protected]>
wrote:

>This is because "nimbus.child.opts" used in "app_config" refers to
>"/external/storm-jmxetric" which is not available as part of apache
>storm-0.9.3 but available in hdp-storm-0.9.3. Then tried removing such
>dependencies from app_config (all process child.opts) and executed, then
>all processes were able to start. But when submitting topologies, there
>are
>some issues while starting 'worker' process. Can you please help me in
>this?
>
>Also, since there seems to be some issue in the packaging step, is there
>any place where I can find the latest updated storm app package for
>0.80-incubating release. (which supports versioning)?
>
>http://public-repo-1.hortonworks.com/HDP/centos6/2.x/GA/2.2.0.0/slider-app
>-packages/storm/slider-storm-app-package-0.9.3.2.2.0.0-2041.zip
> --> package still refers to old release, does not have versioning
>changes.
>
>
>
>On Thu, Jun 11, 2015 at 1:17 AM, Chackravarthy Esakkimuthu <
>[email protected]> wrote:
>
>> Thanks steve, I applied the patch and tried again. Now ended up in some
>> other error preventing NIMBUS to start,
>>
>> Error opening zip file or JAR manifest missing :
>> 
>>/grid/2/hadoop/yarn/local/usercache/yarn/appcache/application_14337762153
>>83_0025/container_1433776215383_0025_01_000002/app/install/apache-storm-0
>>.9.3/external/storm-jmxetric/lib/jmxetric-1.0.4.jar
>> Error occurred during initialization of VM
>> agent library failed to init: instrument
>>
>> I will check about this and update and if you are already aware of this
>> problem, please help me out.
>>
>> Thanks,
>> Chackra
>>
>>
>>
>> On Wed, Jun 10, 2015 at 6:28 PM, Steve Loughran <[email protected]>
>> wrote:
>>
>>>
>>> > On 9 Jun 2015, at 13:10, Chackravarthy Esakkimuthu <
>>> [email protected]> wrote:
>>> >
>>> > I created slider-storm package (with apache storm 0.9.3) following
>>> > instructions at README.txt, and then did install using slider.
>>> >
>>> > NIMBUS component failed to start with following error :
>>> >
>>> > /usr/bin/python: can't open file
>>> >
>>> 
>>>'/grid/2/hadoop/yarn/local/usercache/yarn/appcache/application_143377621
>>>5383_0011/container_1433776215383_0011_01_000002/app/install/apache-stor
>>>m-0.9.3/bin/storm.py':
>>> > [Errno 2] No such file or directory
>>> >
>>> >
>>> > Before that, I was working with HDP slider-storm package (downloaded
>>> from
>>> >
>>> 
>>>http://public-repo-1.hortonworks.com/HDP/debian6/2.x/GA/2.2.0.0/slider-a
>>>pp-packages/storm/slider-storm-app-package-0.9.3.2.2.0.0-2041.zip
>>> )
>>> > and everything was running fine. Do I need to make any change
>>>explicitly
>>> > when I want to use apache distribution?
>>> >
>>> > Because it is expecting storm.py (from slider) to be there inside
>>>storm
>>> > distribution and hence failing.
>>>
>>>
>>>
>>> now that is https://issues.apache.org/jira/browse/SLIDER-658 , "storm
>>> package cannot start storm 0.9.3; "storm.py" not found"
>>>
>>> At some point in the storm development process, the storm launcher
>>>script
>>> changed from  bin/storm to a bin/storm.py. This is what you see in the
>>> storm master branch:
>>> https://github.com/apache/storm/blob/master/bin/storm.py
>>>
>>> the app package script changed to the new one, which worked provided
>>>the
>>> storm release had the new script (which the HDP one clearly has, and
>>>which
>>> you get if you do a storm trunk release)
>>>
>>> I'd thought I'd patched the ASF source to revert back to the old name,
>>> with what my colleagues were releasing internally branched to
>>>storm.py, but
>>> I don't see it theren.
>>>
>>> If you apply the patch in SLIDER-658 everything should sync up again;
>>> later releases of Apache storm will be be back in sync.
>>>
>>> -steve
>>>
>>
>>

Reply via email to