[jira] [Commented] (MESOS-5268) Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
[ https://issues.apache.org/jira/browse/MESOS-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357318#comment-16357318 ] Jie Yu commented on MESOS-5268: --- [~AndyPang] is this still an issue for you? Do you plan to work on that? > Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3 > - > > Key: MESOS-5268 > URL: https://issues.apache.org/jira/browse/MESOS-5268 > Project: Mesos > Issue Type: Bug > Components: containerization >Affects Versions: 0.27.0 > Environment: suse 3.0.101-0.47.71-default #1 SMP Thu Nov 12 12:22:22 > UTC 2015 (b5b212e) x86_64 x86_64 x86_64 GNU/Linux >Reporter: AndyPang >Assignee: AndyPang >Priority: Major > Labels: cgroups > Original Estimate: 48h > Remaining Estimate: 48h > > meson run in SLES 11 sp2 sp3, kernel version 3.0.13/3.076, cpushareisolator > don't take effect. Two framework cpushare proportion is 1:3, we find at last > in mesos container cpu.shares value is right, but when we use "top" to see > result, the cpu usage is not 1:3. Our Application is multithread and can > fulfil the cpu quota when single run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-5268) Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
[
https://issues.apache.org/jira/browse/MESOS-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257686#comment-15257686
]
AndyPang commented on MESOS-5268:
-
I find in mesos cgroup assigin operation are write "cgroup.procs" file ,while
in SLES 11 sp2 sp3 kernel 3.0 have no "cgroup.procs" character,it
reimplantation from community SUSE version kernel 3.2. I have test when write
TGID into cgroup.procs it will not auto write multithread into "tasks".
If I modify both write into "tasks" it will take effect
{code:title=cgroup assigin|borderStyle=solid}
Try assign(const string& hierarchy, const string& cgroup, pid_t pid)
{
return cgroups::write(hierarchy, cgroup, "cgroup.procs", stringify(pid));
}
{code}
> Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
> -
>
> Key: MESOS-5268
> URL: https://issues.apache.org/jira/browse/MESOS-5268
> Project: Mesos
> Issue Type: Bug
> Components: isolation
>Affects Versions: 0.27.0
> Environment: suse 3.0.101-0.47.71-default #1 SMP Thu Nov 12 12:22:22
> UTC 2015 (b5b212e) x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
>Assignee: AndyPang
> Labels: cgroups
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> meson run in SLES 11 sp2 sp3, kernel version 3.0.13/3.076, cpushareisolator
> don't take effect. Two framework cpushare proportion is 1:3, we find at last
> in mesos container cpu.shares value is right, but when we use "top" to see
> result, the cpu usage is not 1:3. Our Application is multithread and can
> fulfil the cpu quota when single run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5268) Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
[
https://issues.apache.org/jira/browse/MESOS-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257679#comment-15257679
]
AndyPang commented on MESOS-5268:
-
I find in mesos cgroup assigin operation
{code:title=cgroup assigin |borderStyle=solid}
Try assign(const string& hierarchy, const string& cgroup, pid_t pid)
{
return cgroups::write(hierarchy, cgroup, "cgroup.procs", stringify(pid));
}
{code}
> Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
> -
>
> Key: MESOS-5268
> URL: https://issues.apache.org/jira/browse/MESOS-5268
> Project: Mesos
> Issue Type: Bug
> Components: isolation
>Affects Versions: 0.27.0
> Environment: suse 3.0.101-0.47.71-default #1 SMP Thu Nov 12 12:22:22
> UTC 2015 (b5b212e) x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
>Assignee: AndyPang
> Labels: patch
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> meson run in SLES 11 sp2 sp3, kernel version 3.0.13/3.076, cpushareisolator
> don't take effect. Two framework cpushare proportion is 1:3, we find at last
> in mesos container cpu.shares value is right, but when we use "top" to see
> result, the cpu usage is not 1:3. Our Application is multithread and can
> fulfil the cpu quota when single run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
