[
https://issues.apache.org/jira/browse/FLUME-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273436#comment-13273436
]
Mubarak Seyed edited comment on FLUME-1199 at 5/11/12 6:05 PM:
---------------------------------------------------------------
For HTTP monitoring, we are planning to embed Jetty 6.26 (with NIO support) for
WebUI and monitoring per agent. We can have multiple app context
(/agent-status, /http-source1, /http-source2, etc). We can build a REST layer
inside agent (as a wrapper) to convert HTTP post request (to Event) and place
it in a channel. If there is enough system resource available (Memory, CPU), we
can embed REST and Agent in same JVM and run as in-process.
HBase REST layer runs out of process with RegionServer, meaning it calls HBase
client API for each request invocation.
was (Author: mubarakseyed):
For HTTP monitoring, we are planning to embed Jetty 6.26 (with NIO support)
for WebUI and monitoring per agent. We can have multiple app context
(/agent-status, /http-source1, /http-source2, etc). We can build a REST layer
inside agent (as a wrapper) to convert HTTP post request (to Event) and place
it in a channel. If there is enough system resource available (Memory, CPU), we
can embed REST and Agent in same JVM and run as in-process.
HBase REST layer runs out of process, meaning it calls HBase client API for
each request invocation.
> Add HTTP Post Source
> --------------------
>
> Key: FLUME-1199
> URL: https://issues.apache.org/jira/browse/FLUME-1199
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Affects Versions: v1.1.0
> Reporter: Roko Kruze
>
> From some clients it would be simpler to post an event to a HTTP URL then to
> make an Avro RPC call. This source would accept inbound HTTP POST requests
> and ideally would place all the HTTP headers into the headers of the event so
> they could be used for routing and partitioning.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
