Return-Path: X-Original-To: apmail-flume-user-archive@www.apache.org Delivered-To: apmail-flume-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 DCF1F17CEB for ; Wed, 18 Feb 2015 16:41:18 +0000 (UTC) Received: (qmail 97282 invoked by uid 500); 18 Feb 2015 16:40:20 -0000 Delivered-To: apmail-flume-user-archive@flume.apache.org Received: (qmail 97230 invoked by uid 500); 18 Feb 2015 16:40:20 -0000 Mailing-List: contact user-help@flume.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flume.apache.org Delivered-To: mailing list user@flume.apache.org Received: (qmail 97220 invoked by uid 99); 18 Feb 2015 16:40:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Feb 2015 16:40:20 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of smaine.kahlouch@arkena.com designates 157.56.112.144 as permitted sender) Received: from [157.56.112.144] (HELO emea01-am1-obe.outbound.protection.outlook.com) (157.56.112.144) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Feb 2015 16:39:55 +0000 Received: from AM3PR04MB0822.eurprd04.prod.outlook.com (10.141.46.17) by AM3PR04MB0824.eurprd04.prod.outlook.com (10.141.46.19) with Microsoft SMTP Server (TLS) id 15.1.87.18; Wed, 18 Feb 2015 16:39:50 +0000 Received: from AM3PR04MB0822.eurprd04.prod.outlook.com ([10.141.46.17]) by AM3PR04MB0822.eurprd04.prod.outlook.com ([10.141.46.17]) with mapi id 15.01.0087.013; Wed, 18 Feb 2015 16:39:50 +0000 From: Smaine KAHLOUCH To: "user@flume.apache.org" Subject: Re: Spreading multiple file-channels over distinct disks Thread-Topic: Spreading multiple file-channels over distinct disks Thread-Index: AQHQS1tT5fpmN6lpvEKIeplBx8IaMZz2mngAgAABgP8= Date: Wed, 18 Feb 2015 16:39:50 +0000 Message-ID: <1424277570918.86352@arkena.com> References: <54E457EA.2040803@smartjog.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [2a00:1080:804:200:eb11:5772:34c0:d861] authentication-results: flume.apache.org; dkim=none (message not signed) header.d=none; x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:AM3PR04MB0824; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:AM3PR04MB0824; x-forefront-prvs: 04916EA04C x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(377454003)(24454002)(53754006)(86362001)(15975445007)(106116001)(19625215002)(46102003)(77156002)(450100001)(62966003)(77096005)(16601075003)(36756003)(2950100001)(2900100001)(102836002)(122556002)(16236675004)(2351001)(19580405001)(19580395003)(54356999)(117636001)(2501002)(87936001)(110136001)(40100003)(76176999)(92566002)(107886001)(19617315012)(19627405001)(2656002)(50986999)(3826002);DIR:OUT;SFP:1102;SCL:1;SRVR:AM3PR04MB0824;H:AM3PR04MB0822.eurprd04.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en; Content-Type: multipart/alternative; boundary="_000_142427757091886352arkenacom_" MIME-Version: 1.0 X-OriginatorOrg: arkena.com X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2015 16:39:50.2307 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: b7b9e5b9-4875-440c-82e2-364b828200ef X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR04MB0824 X-Virus-Checked: Checked by ClamAV on apache.org --_000_142427757091886352arkenacom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thank you Ahmed, i'll try that Regards, Smaine ________________________________ From: Ahmed Vila Sent: Wednesday, February 18, 2015 5:33 PM To: user@flume.apache.org Subject: Re: Spreading multiple file-channels over distinct disks Hi Smaine, There is always an overhead of running multiple flume instances, i.e. multi= ple Java VMs. Thus, I wouldn't recommend running more of them if that's not= due to distribution across servers. But, you are able to do round-robin events from source into multiple channe= ls and those channels could have one disk per channel. However, in that case you'll also need at least one sink per channel. Guess= that's even desirable if you're sinking your data into the HDFS. Regards On Wed, Feb 18, 2015 at 10:14 AM, Smaine Kahlouch > wrote: Hi all! I would like to know what is the best way to spread the i/o on my server. Actually it has several disks and i was wondering how to spread Flume's wor= k over them : * One Flume instance with multiple working directories (dataDirs), each wor= king directory on a single disk * Multiple flume instances with a file channel on a distinct disk (using co= ntainers would be the best way to do so) Could you please helpe me to find out the best architecture which allows us= to keep file-channel for data persistency ? Regards, -- Smaine Kahlouch - Engineer, Research & Engineering Arkena | T: +33 1 5868 6196 27 Blvd Hippolyte Marqu=E8s, 94200 Ivry-sur-Seine, France arkena.com -- Best regards, Ahmed Vila | Senior software developer DevLogic | Sarajevo | Bosnia and Herzegovina Office : +387 33 942 123 Mobile: +387 62 139 348 Website: www.devlogic.eu E-mail : avila@devlogic.eu --------------------------------------------------------------------- This e-mail and any attachment is for authorised use by the intended recipi= ent(s) only. This email contains confidential information. It should not be= copied, disclosed to, retained or used by, any party other than the intend= ed recipient. Any unauthorised distribution, dissemination or copying of th= is E-mail or its attachments, and/or any use of any information contained i= n them, is strictly prohibited and may be illegal. If you are not an intend= ed recipient then please promptly delete this e-mail and any attachment and= all copies and inform the sender directly via email. Any emails that you s= end to us may be monitored by systems or persons other than the named commu= nicant for the purposes of ascertaining whether the communication complies = with the law and company policies. --------------------------------------------------------------------- This e-mail and any attachment is for authorised use by the intended recipi= ent(s) only. This email contains confidential information. It should not be= copied, disclosed to, retained or used by, any party other than the intend= ed recipient. Any unauthorised distribution, dissemination or copying of th= is E-mail or its attachments, and/or any use of any information contained i= n them, is strictly prohibited and may be illegal. If you are not an intend= ed recipient then please promptly delete this e-mail and any attachment and= all copies and inform the sender directly via email. Any emails that you s= end to us may be monitored by systems or persons other than the named commu= nicant for the purposes of ascertaining whether the communication complies = with the law and company policies. --_000_142427757091886352arkenacom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Thank you Ahmed, i'll try that


Regards,

Smaine


From: Ahmed Vila <avila= @devlogic.eu>
Sent: Wednesday, February 18, 2015 5:33 PM
To: user@flume.apache.org
Subject: Re: Spreading multiple file-channels over distinct disks
 
Hi Smaine,

There is always an overhead of running multiple flume instances, i.e. = multiple Java VMs. Thus, I wouldn't recommend running more of them if that'= s not due to distribution across servers.

But, you are able to do round-robin events from source into multiple c= hannels and those channels could have one disk per channel.
However, in that case you'll also need at least one sink per channel. = Guess that's even desirable if you're sinking your data into the HDFS.

Regards

On Wed, Feb 18, 2015 at 10:14 AM, Smaine Kahlouc= h <smain= e.kahlouch@smartjog.com> wrote:
Hi all!

I would like to know what is the best way to spread the i/o on my server. Actually it has several disks and i was wondering how to spread Flume's wor= k over them :
* One Flume instance with multiple working directories (dataDirs), each wor= king directory on a single disk
* Multiple flume instances with a file channel on a distinct disk (using co= ntainers would be the best way to do so)

Could you please helpe me to find out the best architecture which allows us= to keep file-channel for data persistency ?

Regards,

--
Smaine Kahlouch - Engineer, Research & Engineering
Arkena | T: +33 1 5868 6196
27 Blvd Hippolyte Marqu=E8s, 94200 Ivry-sur-Seine, France
arkena.com




--

Best regards,

Ahmed Vila | Senior software developer
DevLogic | Sarajevo | Bosnia and Herzegovina

Office : +387 33 942 123 
Mobile: +387 62 139 348

Website: www= .devlogic.eu 
E-mail   : avila@devlogic.eu
-------------------------------------------------------------= --------
This e-mail and any attachment is for authorised use by the intended recipi= ent(s) only. This email contains confidential information. It should not be= copied, disclosed to, retained or used by, any party other than the intend= ed recipient. Any unauthorised distribution, dissemination or copying of this E-mail or its attachments, and/or any use= of any information contained in them, is strictly prohibited and may be il= legal. If you are not an intended recipient then please promptly delete thi= s e-mail and any attachment and all copies and inform the sender directly via email. Any emails that you s= end to us may be monitored by systems or persons other than the named commu= nicant for the purposes of ascertaining whether the communication complies = with the law and company policies.

-----------------------------------------------------= ----------------
This e-mail and any attachment is for authorised use by the intended recipi= ent(s) only. This email contains confidential information. It should not be= copied, disclosed to, retained or used by, any party other than the intend= ed recipient. Any unauthorised distribution, dissemination or copying of this E-mail or its attachments, and/or any use= of any information contained in them, is strictly prohibited and may be il= legal. If you are not an intended recipient then please promptly delete thi= s e-mail and any attachment and all copies and inform the sender directly via email. Any emails that you s= end to us may be monitored by systems or persons other than the named commu= nicant for the purposes of ascertaining whether the communication complies = with the law and company policies.
--_000_142427757091886352arkenacom_--