Actually, we moved from "LOCAL_ONLY" to PER_CONTAINER.
The parameter should still be for e.g.
"site.storm-site.supervisor.slots.ports":
"[${SUPERVISOR.ALLOCATED_PORT}{PER_CONTAINER},${SUPERVISOR.ALLOCATED_PORT}{PER_CONTAINER}]"
________________________________________
From: Jon Maron <jma...@hortonworks.com>
Sent: Monday, March 30, 2015 10:28 AM
To: dev@slider.incubator.apache.org
Subject: Re: Invalid port 0 for storm instances
We transitioned from “ALLOCATED_PORT” to “PER_CONTAINER” - I just can’t recall
whether that was in the 0.60 timeframe?
— Jon
> On Mar 30, 2015, at 1:21 PM, Sumit Mohanty <sumit.moha...@gmail.com> wrote:
>
> Did you create the storm package yourself? Can you share the appConfig.json
> you are using?
>
> On Mon, Mar 30, 2015 at 10:07 AM, Nitin Aggarwal <
> nitin3588.aggar...@gmail.com> wrote:
>
>> It's a typo just in the mail. It is replaced correctly for some of the
>> supervisors configuration.
>> I am running slider version 0.60.
>>
>> On Mon, Mar 30, 2015 at 10:04 AM, Sumit Mohanty <smoha...@hortonworks.com>
>> wrote:
>>
>>> If the exact text was "ALOOCATED_PORT" then replacing them with
>>> "ALLOCATED_PORT" might solve it.
>>>
>>> Otherwise, whats the version of Slider are you using?
>>> ________________________________________
>>> From: Nitin Aggarwal <nitin3588.aggar...@gmail.com>
>>> Sent: Monday, March 30, 2015 9:51 AM
>>> To: dev@slider.incubator.apache.org
>>> Subject: Invalid port 0 for storm instances
>>>
>>> Hi,
>>>
>>> I am trying to run storm cluster with 200 instances, using Slider. While
>>> submitting topologies to the cluster, some of the workers failed to start
>>> due to error.
>>>
>>> 2015-03-27T13:27:40.168-0400 b.s.event [ERROR] Error when processing
>> event
>>> java.lang.IllegalArgumentException: invalid port: 0
>>> at backtype.storm.security.auth.ThriftClient.<init>(ThriftClient.java:54)
>>> ~[storm-core-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
>>> at backtype.storm.utils.NimbusClient.<init>(NimbusClient.java:47)
>>> ~[storm-core-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
>>> at backtype.storm.utils.NimbusClient.<init>(NimbusClient.java:43)
>>> ~[storm-core-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
>>> at
>>>
>> backtype.storm.utils.NimbusClient.getConfiguredClient(NimbusClient.java:36)
>>> ~[storm-core-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
>>> at backtype.storm.utils.Utils.downloadFromMaster(Utils.java:253)
>>> ~[storm-core-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
>>> at backtype.storm.daemon.supervisor$fn__6900.invoke(supervisor.clj:482)
>>> ~[storm-core-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
>>> at clojure.lang.MultiFn.invoke(MultiFn.java:241) ~[clojure-1.5.1.jar:na]
>>> at
>>>
>>>
>> backtype.storm.daemon.supervisor$mk_synchronize_supervisor$this__6820.invoke(supervisor.clj:371)
>>> ~[storm-core-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
>>> at backtype.storm.event$event_manager$fn__2825.invoke(event.clj:40)
>>> ~[storm-core-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
>>> at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
>>> at java.lang.Thread.run(Thread.java:724) [na:1.7.0_40]
>>>
>>> I found that some of the supervisors don't have the correct
>> configurations.
>>> Their configuration, still have markers like ${NIMBUS_HOST},
>>> ${NIMBUS.ALOOCATED_PORT}.
>>>
>>> Are these markers expected in supervisor storm configuration ?
>>>
>>> Thanks
>>> Nitin
>>>
>>
>
>
>
> --
> thanks
> Sumit
