incubator-s4-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Morel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (S4-91) Runtime isolation
Date Thu, 20 Sep 2012 17:54:08 GMT

    [ https://issues.apache.org/jira/browse/S4-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459794#comment-13459794
] 

Matthieu Morel commented on S4-91:
----------------------------------

Note that this was also discussed some time ago: http://mail-archives.apache.org/mod_mbox/incubator-s4-dev/201204.mbox/thread
and http://mail-archives.apache.org/mod_mbox/incubator-s4-dev/201205.mbox/thread

To summarize, there are 2 designs for achieving isolation: 
# using different apps and interconnecting them. This is easy with the dynamic registration
mechanism for external streams in 0.5
# controlling node allocation on a PE basis. This is more fine grained and requires development.
Hence this ticket.
                
> Runtime isolation
> -----------------
>
>                 Key: S4-91
>                 URL: https://issues.apache.org/jira/browse/S4-91
>             Project: Apache S4
>          Issue Type: Task
>            Reporter: Aimee Cheng
>             Fix For: 0.6
>
>
> We would like to use runtime isolation. PEs from the same APP can split to several sub-sets
and run in different JVM processes, so that we might get some benefit from it, such as isolating
the PEs which cost a lot of resources, easier to find out the PE with problem. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message