[
https://issues.apache.org/jira/browse/FALCON-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369842#comment-14369842
]
Ajay Yadava commented on FALCON-1108:
-------------------------------------
[~sriksun] I assume you are talking about isolation between cooking of
different recipes. Each request can be handled in a separate thread like an
http server manages isolation between different requests. Do you see any
special challenges in cooking recipes using this approach which can be avoided
by launching separate JVMs?
Launching a separate JVM IMHO can become a maintainability and operability
issue. I also feel it will be a more resource intensive approach and the
isolation is not as strong as it's on same physical machine as main falcon
server and falcon does need to throttle/launch/track different JVMs for recipe
cooking.
We can have better isolation if we are able to easily deploy recipes server on
a different box. This approach can also scale linearly by adding more machines
if needed. There will be a better code separation also as main falcon server
doesn't need to have code to communicate or track the status of the launched
JVMs or to serve recipes to clients. Falcon server will also not need to
maintain throttling for recipe requests. Like a web-server recipe server can
deny more connections in case of being overloaded through configurations.
> Custom recipe processing
> ------------------------
>
> Key: FALCON-1108
> URL: https://issues.apache.org/jira/browse/FALCON-1108
> Project: Falcon
> Issue Type: Sub-task
> Affects Versions: 0.6
> Reporter: Sowmya Ramesh
> Labels: Recipe
> Fix For: 0.7
>
>
> Custom recipe cooking to be done on the server side in a separate independent
> process than Falcon process I.e. It runs in a different JVM. For more details
> refer [FALCON-1107|https://issues.apache.org/jira/browse/FALCON-1107]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
