Return-Path: X-Original-To: apmail-hama-user-archive@www.apache.org Delivered-To: apmail-hama-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C9BC810AD1 for ; Thu, 6 Feb 2014 05:09:59 +0000 (UTC) Received: (qmail 58257 invoked by uid 500); 6 Feb 2014 05:09:59 -0000 Delivered-To: apmail-hama-user-archive@hama.apache.org Received: (qmail 58072 invoked by uid 500); 6 Feb 2014 05:09:58 -0000 Mailing-List: contact user-help@hama.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hama.apache.org Delivered-To: mailing list user@hama.apache.org Received: (qmail 58058 invoked by uid 99); 6 Feb 2014 05:09:56 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Feb 2014 05:09:56 +0000 Received: from localhost (HELO mail-ob0-f182.google.com) (127.0.0.1) (smtp-auth username edwardyoon, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Feb 2014 05:09:56 +0000 Received: by mail-ob0-f182.google.com with SMTP id wm4so1670241obc.13 for ; Wed, 05 Feb 2014 21:09:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=EU0SKXxOxXrmg1PSYd5/JoMURrVhv2Fbujdwkrt9nq8=; b=hbj0GiiAG8Nlq/d5lcQdK1J3zB0EnstIfj3lHgiPga45bcPTbxpIqfyzkiMhbzsaOT 0+opzKMjD64OOZeh6Ds4aMcxvV02BAu4IM7lCLFwaUOp493czOK+1hPp4glg+xDA1LHQ gnvESVNDIqp5hDZpz8CnJm5HRtThK1DJMCuUCow6dEPXqBqT1jpqRF/YH/PYTwEq29Ra IXX+vOA0aZwEJKQCHwQLd1aojMls8cgsLWCQ5KiTS+M8+NeDPpLHhbs9SWB825DMY01G bTxWx9I5RVxi6UU+ixTtu9KE07opVg5xuaCX5Zf4HPEBd4+/KZ4rlu3KY9DBDKC4kmTn isCg== X-Gm-Message-State: ALoCoQnSETdVBQFPZsi2tecjUvyfxP0b+ZkYf1QdY6qBhSLB51KxmXS/knU20mXnwmJbLyNiq3uP MIME-Version: 1.0 X-Received: by 10.182.113.195 with SMTP id ja3mr4931133obb.46.1391663395234; Wed, 05 Feb 2014 21:09:55 -0800 (PST) Received: by 10.60.83.196 with HTTP; Wed, 5 Feb 2014 21:09:55 -0800 (PST) In-Reply-To: <52F238E3.8010700@csd.auth.gr> References: <52F22A5B.8090605@csd.auth.gr> <52F238E3.8010700@csd.auth.gr> Date: Thu, 6 Feb 2014 14:09:55 +0900 Message-ID: Subject: Re: Groomservers IPC server port range From: "Edward J. Yoon" To: "user@hama.apache.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Oh, .. thanks. The GroomServer.taskReportServer seems uses random port. I'll make it configurable. On Wed, Feb 5, 2014 at 10:13 PM, =CE=97=CE=BB=CE=AF=CE=B1=CF=82 =CE=9A=CE= =B1=CF=80=CE=BF=CF=85=CF=81=CE=AC=CE=BD=CE=B7=CF=82 = wrote: > Hey, > > So what the IPC Server stands for and it gets random ports? I ve seen 398= 65 > and 52765. What is the deal with it? > > > =CE=A3=CF=84=CE=B9=CF=82 5/2/2014 2:53 =CE=BC=CE=BC, =CE=BF/=CE=B7 Edward= J. Yoon =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5: > >> Hi, >> >> a Hama cluster uses ports "bsp.master.port" 40000 and >> "bsp.groom.rpc.port" 50000 to communicate among the cluster nodes. >> >> And the default peer port is 61000. If you set 3 for the maximum >> number of tasks per node, each task uses ports from 61000 to 61003 to >> transfer messages between bsp tasks. >> >> On Wed, Feb 5, 2014 at 9:11 PM, =CE=97=CE=BB=CE=AF=CE=B1=CF=82 =CE=9A=CE= =B1=CF=80=CE=BF=CF=85=CF=81=CE=AC=CE=BD=CE=B7=CF=82 >> wrote: >>> >>> Hello there, >>> >>> I am trying to setup Hama in a cluster with really strict port >>> permissions >>> and I get across the error at every GroomServer: >>> "There is a problem in establishing link with BSPMaster." >>> >>> - Do you know what is the range of ports that every GroomServers IPC >>> Server >>> gets when started? >>> - Is there a way to limit this range to new user values? >>> >>> Thank you. >> >> >> > --=20 Best Regards, Edward J. Yoon @eddieyoon