@Nathan Leung,i want just want limit the max works num,then set spout,blot nums,then observe the infos when total nums larger than max nums or less than max nums. Thanks， Lax
Date: Thu, 17 Jul 2014 12:08:48 -0400 Subject: RE: could assign Topology execute in some supervisor From: [email protected] To: [email protected] Yes requesting 55 workers when you only have 14 is not going to work so well. Why do you set number of workers so high for your topology? On Jul 17, 2014 8:14 AM, "chenlax" <[email protected]> wrote: @Nathan Leung,i think i know why isolation scheduler unwork in my demo. in the topology i set setNumWorkers(55),but a supervisor's slots only 14,so when i submit topology,it will work until wait for enough resources. Thanks， Lax From: [email protected] To: [email protected] Subject: RE: could assign Topology execute in some supervisor Date: Tue, 15 Jul 2014 17:41:27 +0800 yes, i restart nimbus after change conf. Thanks， Lax Date: Fri, 11 Jul 2014 11:35:07 -0400 Subject: Re: could assign Topology execute in some supervisor From: [email protected] To: [email protected] as a sanity check, did you restart your nimbus? On Thu, Jul 10, 2014 at 9:53 PM, chenlax <[email protected]> wrote: Nathan Leung， i add the isolation conf as follow: storm.scheduler: "backtype.storm.scheduler.IsolationScheduler" isolation.scheduler.machines: "hellotest": 1 and submit topology dosen't has any error log or warm log. Thanks， Lax Date: Thu, 10 Jul 2014 10:32:10 -0400 Subject: Re: could assign Topology execute in some supervisor From: [email protected] To: [email protected] Your yaml doesn't appear to be properly formatted. Either that, or your email client stripped some characters. On Thu, Jul 10, 2014 at 4:16 AM, chenlax <[email protected]> wrote: and submit other topology also can't get works. Thanks， Lax From: [email protected] To: [email protected] Subject: RE: could assign Topology execute in some supervisor Date: Thu, 10 Jul 2014 16:14:12 +0800 i try use isolation.scheduler,but when i submit topology,the topology can't get any works. Cluster SummaryVersionNimbus uptimeSupervisors Used slotsFree slotsTotal slotsExecutorsTasks0.8.24m 12s30424200 Topology summaryNameIdStatusUptimeNum workersNum executorsNum taskshellotest hellotest-2-1404979653ACTIVE58s000 Nimbus conf: isolation.scheduler.machines{"hellotest" 1} Thanks， Lax Date: Tue, 8 Jul 2014 09:07:27 -0400 Subject: RE: could assign Topology execute in some supervisor From: [email protected] To: [email protected] Does the isolation scheduler suit your needs? https://storm.incubator.apache.org/2013/01/11/storm082-released.html On Jul 8, 2014 8:53 AM, "chenlax" <[email protected]> wrote: i means assign 2 supervisor machines execute a topology,the worker number more than 2.maybe 10 or more. Thanks， Lax Date: Tue, 8 Jul 2014 08:11:30 -0400 Subject: Re: could assign Topology execute in some supervisor From: [email protected] To: [email protected] yes, config.setNumWorkers(2); this will run 2 worker processes, usually on 2 separate supervisor machines. On Tue, Jul 8, 2014 at 6:12 AM, chenlax <[email protected]> wrote: The Storm has 8 supervisors,i want assign a topology run in 2 superviosrs,and the 2 supercisor only execute the topology. how can i do it? Thanks， Lax -- Tomas Mazukna 678-557-3834
