[jira] [Commented] (SLIDER-1104) failed to track a outstanding request which was escalated

[ https://issues.apache.org/jira/browse/SLIDER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292358#comment-15292358 ] Nitin Aggarwal commented on SLIDER-1104: Any updates for this ? > fa

Re: Invalid port 0 for storm instances

host and port information would be propagated to already running supervisors? On Sat, Apr 11, 2015 at 8:19 AM, Gour Saha wrote: > There were no issues. The variable was renamed to be more user friendly. > > -Gour > > On 4/10/15, 3:48 PM, "Nitin Aggarwal" > wrote

Re: Invalid port 0 for storm instances

I think even DEF_ZK_PATH should be DEFAULT_ZK_PATH > ____ > From: Nitin Aggarwal > Sent: Monday, March 30, 2015 10:38 AM > To: dev@slider.incubator.apache.org > Subject: Re: Invalid port 0 for storm instances > > Yes, storm package is built internally. >

Re: Invalid port 0 for storm instances

ations" : "false", "site.storm-site.topology.sleep.spout.wait.strategy.time.ms" : "1", "site.storm-site.topology.spout.wait.strategy" : "backtype.storm.spout.SleepSpoutWaitStrategy", "site.storm-site.topology.state.synchr

Re: Invalid port 0 for storm instances

CATED_PORT" might solve it. > > Otherwise, whats the version of Slider are you using? > ____ > From: Nitin Aggarwal > Sent: Monday, March 30, 2015 9:51 AM > To: dev@slider.incubator.apache.org > Subject: Invalid port 0 for storm instances &

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 ba

Re: Locality results in instance shut-down due to single bad instance

tune this -maybe- but it gets complex. > > >>> > > >>> 1. If the placement policy is STRICT, then we must ask for that > > previously > > >>> used node. (Though thinking about it, the component must have started > > at > > >

Re: Locality results in instance shut-down due to single bad instance

"yarn.component.instances": "1", > > "yarn.memory": "1500", > > "yarn.component.placement.policy": "2" > > }, > > > > -Gour > > > > On Tue, Jan 6, 2015 at 3:33 PM, Nitin Aggarwal &l

Locality results in instance shut-down due to single bad instance

failures, when failure threshold is reached (which is currently also not reset correctly. SLIDER-629), it triggers instance shut-down. Is there a way to give up locality, in case of multiple failures, to avoid this scenario ? Thanks Nitin Aggarwal

Bringing up HBase cluster with Slider

Hi, I was trying to bring hbase cluster with Slider. As we have non-yarn HBase installation also on the machines, I faced issue due to HBASE_HOME variable not set correctly. I resolved it by setting it explicitly in "app-packages/hbase/package/templates/hbase-env.sh.j2" as export HBASE_HOME={{hba