GitHub user harishreedharan opened a pull request:
https://github.com/apache/spark/pull/807
SPARK-1729. Make Flume pull data from source, rather than the current pu...
...sh model
Currently Spark uses Flume's internal Avro Protocol to ingest data from
Flume. If the executor running the
receiver fails, it currently has to be restarted on the same node to be
able to receive data.
This commit adds a new Sink which can be deployed to a Flume agent. This
sink can be polled by a new
DStream that is also included in this commit. This model ensures that data
can be pulled into Spark from
Flume even if the receiver is restarted on a new node. This also allows the
receiver to receive data on
multiple threads for better performance.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harishreedharan/spark master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/807.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #807
----
commit 6d6776a45f30e3594a15bda2582f99819c28a583
Author: Hari Shreedharan <[email protected]>
Date: 2014-05-09T06:16:56Z
SPARK-1729. Make Flume pull data from source, rather than the current push
model
Currently Spark uses Flume's internal Avro Protocol to ingest data from
Flume. If the executor running the
receiver fails, it currently has to be restarted on the same node to be
able to receive data.
This commit adds a new Sink which can be deployed to a Flume agent. This
sink can be polled by a new
DStream that is also included in this commit. This model ensures that data
can be pulled into Spark from
Flume even if the receiver is restarted on a new node. This also allows the
receiver to receive data on
multiple threads for better performance.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
