[prev in list] [next in list] [prev in thread] [next in thread] 

List:       flume-user
Subject:    Sizing of Flume and resiliency
From:       Rani Yaroshinski <rani.yaroshinski () gmail ! com>
Date:       2015-07-29 8:20:44
Message-ID: CACQ=AYvtjDf=Lz9ef=krbzvWT6OeHkp3z866QCKFWB_-iSud5w () mail ! gmail ! com
[Download RAW message or body]

Hi all,

suppose I am using flume for the sake of transferring events from different
and complex sources
into HDFS sink mainly.

I am looking for some baseline paper for sizing flume installation, since
the only relevant material
for this, is dealing with event aggregations which are not needed by me.

I am looking for sizing from the point of view of memory, core and I/O
according
to the event's characteristicsm the number of sources and the number of
channels.

Another issue, which still falls into this section of architectural and
non-functional considerations
is the issue of fail over and resiliency.
I can see failover only for sinks, but not for channel, not for sources,
and not for agents, and machines running the flume-agent instance.

Regards,
Rani

[Attachment #3 (text/html)]

<div dir="ltr">Hi all,<div><br></div><div>suppose I am using flume for the sake of \
transferring events from different and complex sources</div><div>into HDFS sink \
mainly.</div><div><br></div><div>I am looking for some baseline paper for sizing \
flume installation, since the only relevant material</div><div>for this, is dealing \
with event aggregations which are not needed by me.</div><div><br></div><div>I am \
looking for sizing from the point of view of memory, core and I/O \
according</div><div>to the event&#39;s characteristicsm the number of sources and the \
number of channels.</div><div><br></div><div>Another issue, which still falls into \
this section of architectural and non-functional considerations  </div><div>is the \
issue of fail over and resiliency.</div><div>I can see failover only for sinks, but \
not for channel, not for sources, and not for agents, and machines running the \
flume-agent instance.</div><div><br></div><div>Regards,</div><div>Rani</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]