Re: Supported Storm version

Hey guys, thanks for your help so far. I've been able to deploy slider start it properly and now I'm trying to deploy storm app. I'm using the zip that Panagiotis suggested but I'm getting this error when it tries to deploy 2017-01-13 16:38:22,231 [1269430493@qtp-1276410298-5] INFO agent.AgentProv

Re: Supported Storm version

Are you specifying the square brackets "[ ]" in the port range? If yes, then you need to remove them. Just specify the integers (comma separated). -Gour On 1/13/17, 8:59 AM, "Telles Nobrega" wrote: >Hey guys, thanks for your help so far. I've been able to deploy slider >start it properly and no

Re: Supported Storm version

I'm actually not specifying those values, I don't know where they come from. I'm using plaingly the zip file that Panagiotis showed me. On Fri, Jan 13, 2017 at 2:22 PM, Gour Saha wrote: > Are you specifying the square brackets "[ ]" in the port range? If yes, > then you need to remove them. Just

Re: Supported Storm version

This is in the appConfig-default.json "site.storm-site.supervisor.slots.ports": "[${SUPERVISOR.ALLOCATED_PORT}{PER_CONTAINER},${SUPERVISOR.ALLOCATED_PORT}{PER_CONTAINER}]" Maybe the brackets placement is wrong? On Fri, Jan 13, 2017 at 2:30 PM, Telles Nobrega wrote: > I'm actually not specifying

Re: Supported Storm version

It looks like that is the correct format for the storm property. Is the AM stopping after displaying this message, or does it continue normally? In the current version of AgentProviderService, it looks like the error is caught and logged ( https://github.com/apache/incubator-slider/blob/develop/sli

Re: Supported Storm version

It continues working, but it fails to start nimbus after 6 tries. Here is the full log . I had a small cluster and it was failing to deploy from the start, now I increased the size and it fails by the log, could this be environment issue? Thanks On Fri, J

Re: Supported Storm version

You are right Billie. I confused this with site.global.slider.allowed.ports. I remember that the storm-app supports this weird format of ports specified with square brackets. Slider just tries to parse and logs it at WARN level and moves on and let¹s the app handle it. Telles, Are you seeing any

Re: Supported Storm version

Hi Gour, I pasted the log on the previous email, it keeps trying to deploy the services, but it fails. On Fri, Jan 13, 2017 at 2:53 PM, Gour Saha wrote: > You are right Billie. I confused this with > site.global.slider.allowed.ports. > > I remember that the storm-app supports this weird format o

Re: Supported Storm version

Apperantly the paste didn't get the whole log, I'm sending as an attachment. On Fri, Jan 13, 2017 at 2:55 PM, Telles Nobrega wrote: > Hi Gour, I pasted the log on the previous email, it keeps trying to deploy > the services, but it fails. > > On Fri, Jan 13, 2017 at 2:53 PM, Gour Saha wrote: >

Re: Supported Storm version

Attachments to apache DLs are dropped. So we cannot get them. Can you look at the agent logs for one of the NIMBUS containers? -Gour From: Telles Nobrega mailto:tenob...@redhat.com>> Reply-To: "dev@slider.incubator.apache.org" mailto:dev@slider.incubator

Re: Supported Storm version

Hi Gour, I can certainly try. Is there an easy way to find where the containers are allocated? On Fri, Jan 13, 2017 at 3:03 PM, Gour Saha wrote: > Attachments to apache DLs are dropped. So we cannot get them. Can you look > at the agent logs for one of the NIMBUS containers? > > -Gour > > From:

Re: Supported Storm version

Hello Telles, I think I have been through this issue before. This commit might be helpful to you! Cheers, Panagiotis On Fri, Jan 13, 2017 at 6:15 PM, Telles Nobrega wrote: > Hi Gour, I can certainly tr

Re: Supported Storm version

Gour, found this on nimbus.log Traceback (most recent call last): File "/tmp/hadoop-hadoop/nm-local-dir/usercache/hadoop/appcache/application_1483970960290_0005/container_1483970960290_0005_01_02/app/install/apache-storm-0.10.0.2.3.2.0-2950/bin/storm.py", line 560, in main() File "/tm

Re: Supported Storm version

Thanks. I have to apply that and build a new storm zip file correct? On Fri, Jan 13, 2017 at 3:21 PM, Panagiotis Garefalakis wrote: > Hello Telles, > > I think I have been through this issue before. > This commit > 0fefb9d5be0e09e4dc5429c763

Re: Supported Storm version

Looks like it is some sort of a java_home problem. I found Execute['/usr/jdk64/jdk1.7.0_67/bin/jps -vl | grep "^[0-9 ]*backtype.storm.daemon.nimbus" | grep container_1483970960290_0005_01_02 | awk '{print $1}' > /tmp/hadoop-hadoop/nm-local-dir/usercache/hadoop/appcache/application_148397096029

Re: Supported Storm version

Sadly the value is properly set on slider-env.json On Fri, Jan 13, 2017 at 3:36 PM, Telles Nobrega wrote: > Looks like it is some sort of a java_home problem. I > found Execute['/usr/jdk64/jdk1.7.0_67/bin/jps -vl | grep "^[0-9 > ]*backtype.storm.daemon.nimbus" | grep container_1483970960290_0005

Re: Supported Storm version

You should adjust the java_home in the appConfig.json used to create the storm app: https://github.com/apache/incubator-slider/blob/develop/app-packages/storm/appConfig-default.json#L7 On Fri, Jan 13, 2017 at 10:36 AM, Telles Nobrega wrote: > Looks like it is some sort of a java_home problem. I

Re: Supported Storm version

Thanks, I'm checking if it works. On Fri, Jan 13, 2017 at 4:13 PM, Billie Rinaldi wrote: > You should adjust the java_home in the appConfig.json used to create the > storm app: > https://github.com/apache/incubator-slider/blob/develop/ > app-packages/storm/appConfig-default.json#L7 > > On Fri, J