Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 61493200B74 for ; Thu, 1 Sep 2016 18:53:02 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5FA76160AB5; Thu, 1 Sep 2016 16:53:02 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 807BA160AA8 for ; Thu, 1 Sep 2016 18:53:01 +0200 (CEST) Received: (qmail 92402 invoked by uid 500); 1 Sep 2016 16:53:00 -0000 Mailing-List: contact user-help@storm.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.apache.org Delivered-To: mailing list user@storm.apache.org Received: (qmail 92349 invoked by uid 99); 1 Sep 2016 16:53:00 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2016 16:53:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 00C75C000A for ; Thu, 1 Sep 2016 16:53:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -13.801 X-Spam-Level: X-Spam-Status: No, score=-13.801 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_DEF_WHITELIST=-15] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=yahoo-inc.com header.b=b9lldWS1; dkim=pass (1024-bit key) header.d=yahoo-inc.com header.b=r+zf5Sj7 Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id N2SJiEcMBzls for ; Thu, 1 Sep 2016 16:52:57 +0000 (UTC) Received: from mrout4.yahoo.com (mrout4.yahoo.com [216.145.54.109]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 7A0FF5FBA2 for ; Thu, 1 Sep 2016 16:52:56 +0000 (UTC) Received: from omp1029.mail.ne1.yahoo.com (omp1029.mail.ne1.yahoo.com [98.138.89.173]) by mrout4.yahoo.com (8.15.2/8.15.2/y.out) with ESMTPS id u81GqlNf030361 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 1 Sep 2016 09:52:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1472748768; bh=q3afc1n3qdGBL7XF98UcIjv5RXXHwCMg5IskCBDMiNM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject; b=b9lldWS16eeZlvkkIef0swFBAxquiAGxFnXt3zakCVs0D9EqJpe7sAs6cqW9hWW0Q wK7yFjCxQMR24m5wAf0QxZOniNQMVUQgV+88JXR2N4X9pvCc7waJMsQgLcnY8V7GUN AhMjB4nPMMsXWWt49SBtXdg9JKlVJB+Kd48qlS+o= Received: (qmail 60749 invoked by uid 1000); 1 Sep 2016 16:52:47 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo-inc.com; s=ginc1024; t=1472748767; bh=kEhs+QzHN8SRRMcZcCcuVSCYYWFIKTEjXjpV4wlAV6w=; h=Date:From:Reply-To:To:Cc:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type; b=r+zf5Sj7/pszbPXZciW5nQgYohsa5myrDmLZbq0bXmx/Ymi2FScqOENMhNdimXXst1x2Cwm/j3ai491aHuEPHYDsS5GJL6Olc3I8ZrcQILc3sKTZFhWBvkOtHa/OjrVZW91aQKkxDKgetLuSqHpGqWa0BP6l+4DgRcmIzYEMRhQ= Received: from jws10075.mail.ne1.yahoo.com by sendmailws120.mail.ne1.yahoo.com; Thu, 01 Sep 2016 16:52:47 +0000; 1472748767.412 Date: Thu, 1 Sep 2016 16:52:44 +0000 (UTC) From: Kyle Nusbaum Reply-To: Kyle Nusbaum To: "user@storm.apache.org" Cc: Walid Aljoby Message-ID: <781633435.3331952.1472748764591@mail.yahoo.com> In-Reply-To: References: <1707997147.2771218.1472648050470.ref@mail.yahoo.com> <1707997147.2771218.1472648050470@mail.yahoo.com> <1203963932.2785957.1472649027649@mail.yahoo.com> <817655087.2739877.1472667267961@mail.yahoo.com> Subject: Re: Assignment of threads to tcp ports MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3331951_2003625577.1472748764585" archived-at: Thu, 01 Sep 2016 16:53:02 -0000 ------=_Part_3331951_2003625577.1472748764585 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yep! That's correct.=20 If you implemented your own scheduler, you could write one that gave more c= ontrol of ports to the cluster users, but it's not a simple task. =C2=A0-- Kyle=20 On Thursday, September 1, 2016 3:35 AM, Richards Peter wrote: =20 Is it the pluggable scheduler that is being discussed here? http://storm.apache.org/releases/1.0.1/Storm-Scheduler.html Richards Peter. On Wed, Aug 31, 2016 at 11:44 PM, Kyle Nusbaum wro= te: There's no API to do that currently. It's entirely up to the scheduler and = will likely stay that way. I think creating an API to control this sort of = thing is a direction we don't want to go in with Storm.=C2=A0-- Kyle=20 On Wednesday, August 31, 2016 8:10 AM, Walid Aljoby wrote: =20 Hi Anshu, Yeah, correct. (6700-6703).=C2=A0 - Thanks and Best=C2=A0Walid From: anshu shukla To: user@storm.apache.org; Walid Aljoby =20 Sent: Wednesday, August 31, 2016 9:00 PM Subject: Re: Assignment of threads to tcp ports =20 By tcp port you mean Supervisor port . On Wed, Aug 31, 2016 at 6:24 PM, Walid Aljoby wrot= e: Hi everyone, Is it easier to specify in which tcp port the tasks (threads) will be assig= ned?Any API can help to do that? Thank You--Regards --=20 Thanks & Regards, Anshu Shukla =20 =20 =20 ------=_Part_3331951_2003625577.1472748764585 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yep! That's co= rrect.

If you implemented your own scheduler,= you could write one that gave more control of ports to the cluster users, = but it's not a simple task.
 
-- Kyle


On Thursday, September 1, 2016 3:35 AM, Richards Peter <hbkrich= ards@gmail.com> wrote:


Is it the plu= ggable scheduler that is being discussed here?
http://storm.apache.org/releases/1.0.1= /Storm-Scheduler.html

Richar= ds Peter.

On Wed, Aug 31, 2016 at 1= 1:44 PM, Kyle Nusbaum <knusbaum@yahoo-inc.com> wrote:
There's no API to = do that currently. It's entirely up to the scheduler and will likely stay t= hat way. I think creating an API to control this sort of thing is a directi= on we don't want to go in with Storm.
&nbs= p;
-- Kyle


On Wednesday, August 31, 2016 8:10 AM, Walid Aljoby = <walid_aljoby= @yahoo.com> wrote:


= Hi Anshu,

Yeah, correct. (6700-6703). 

-
Thanks and Best 
Walid


=
From: anshu shuk= la <anshushuk= la0@gmail.com>
To: = user@storm.apache.org; Walid Aljoby <walid_aljoby@yahoo.com>
Sent: Wednesday, August= 31, 2016 9:00 PM
S= ubject: Re: Assignment of threads to tcp ports

By tcp port yo= u mean Supervisor port .

On Wed, Aug= 31, 2016 at 6:24 PM, Walid Aljoby <walid_aljoby@yahoo.com> wrote:
Hi everyone,

Is it easier to = specify in which tcp port the tasks (threads) will be assigned?
Any API can help to do that?

=
Thank You
--
Regards



<= /div>--
Thanks & Regards,
Anshu Shukla







------=_Part_3331951_2003625577.1472748764585--