[
https://issues.apache.org/jira/browse/S4-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473031#comment-13473031
]
Aimee Cheng commented on S4-91:
-------------------------------
I think design 2 is a better choice. From a user's perspective, they may prefer
a simple deployment.
So providing an flexible way is important, and we also have some discusses
about that in mail.
1. allow users can control the PE partition.
Because PEs have different requirement of CPU or Memory resources, allow user
to set different node allocations for them is a good way to avoid a potential
performance bottleneck. Under most situations, users may not care about which
specific partition to run exclusive PE, instead, they only care about use how
many partitions to run their PE. So in our opinion, given a total number of
partitions is more practical.
2. exclusive PE allocation
we totally agree the "exclusive allocation" mode,so that some CPU/Memory
sensitive PEs can have their own processes without effect on the others, also
it may provide an easy way for finding root cause PE when met issues. But we
also want to know if it is practicable to provide a "non-exclusive allocation"
mode. The implement seems will turn on to the ratio between partition numbers
at last.
> 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
