[jira] [Created] (MESOS-8061) mesos-slave coredump, crash

[y123456yz (JIRA)]

y123456yz created MESOS-8061:


 Summary: mesos-slave coredump, crash
 Key: MESOS-8061
 URL: https://issues.apache.org/jira/browse/MESOS-8061
 Project: Mesos
  Issue Type: Bug
  Components: allocation, executor, fetcher, stout
Affects Versions: 1.1.0
 Environment: root@ob-slave-489.gz01:/home/coresave$ 
/usr/sbin/mesos-slave --version
mesos 1.1.0
root@ob-slave-489.gz01:/home/coresave$ 
root@ob-slave-489.gz01:/home/coresave$ uname -a
Linux ob-slave-489.gz01 3.10.0-514.16.1.el7.x86_64 #1 SMP Wed Apr 12 15:04:24 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Reporter: y123456yz


root@ob-slave-489.gz01:/home/coresave$ gdb  /usr/sbin/mesos-slave  
./core.mesos-slave.1402.1506722274 
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/sbin/mesos-slave...(no debugging symbols 
found)...done.
[New LWP 1402]
[New LWP 1932]
[New LWP 1941]
[New LWP 1931]
[New LWP 1946]
[New LWP 1935]
[New LWP 1936]
[New LWP 1934]
[New LWP 1938]
[New LWP 1939]
[New LWP 1940]
[New LWP 1943]
[New LWP 1945]
[New LWP 1942]
[New LWP 1933]
[New LWP 1947]
[New LWP 1944]
[New LWP 1948]
[New LWP 1949]
[New LWP 1937]
[New LWP 1954]
[New LWP 1950]
[New LWP 1952]
[New LWP 1951]
[New LWP 1953]
[New LWP 1955]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/mesos-slave 
--master=zk://fd-mesos-zk00.gz01:2181,fd-mesos-zk01.gz01:'.
Program terminated with signal 6, Aborted.
#0  0x7ff0a10605f7 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install 
mesos-1.1.0-2.0.107.centos701406.x86_64
(gdb) bt
#0  0x7ff0a10605f7 in raise () from /lib64/libc.so.6
#1  0x7ff0a1061ce8 in abort () from /lib64/libc.so.6
#2  0x7ff0a32df329 in google::logging_fail() () from /lib/libmesos-1.1.0.so
#3  0x7ff0a32e0e7d in google::LogMessage::Fail() () from 
/lib/libmesos-1.1.0.so
#4  0x7ff0a32e2bbc in google::LogMessage::SendToLog() () from 
/lib/libmesos-1.1.0.so
#5  0x7ff0a32e0a6c in google::LogMessage::Flush() () from 
/lib/libmesos-1.1.0.so
#6  0x7ff0a32e0c79 in google::LogMessage::~LogMessage() () from 
/lib/libmesos-1.1.0.so
#7  0x7ff0a32e1be2 in google::ErrnoLogMessage::~ErrnoLogMessage() () from 
/lib/libmesos-1.1.0.so
#8  0x7ff0a325f9c2 in process::initialize(Option const&, 
Option const&, Option const&) () from 
/lib/libmesos-1.1.0.so
#9  0x0040fca9 in main ()
(gdb) quit



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7885) how to get the mesos-containerizer log-info

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7885:
--

[~kaysoky]
your answer is very helpful for me.
thanks 

> how to get the mesos-containerizer log-info
> ---
>
> Key: MESOS-7885
> URL: https://issues.apache.org/jira/browse/MESOS-7885
> Project: Mesos
>  Issue Type: Bug
>  Components: executor
>Affects Versions: 1.2.0
>Reporter: y123456yz
>
> how to get the mesos-containerizer log-info
> I don't find the log info of mesos-containerizer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7885) how to get the mesos-containerizer log-info

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7885:
--

I set the --log_dir=/var/log/mesos when I run mesos.
but many log not be writed to /var/log/mesos, how to get all the debug message 
of mesos, example the log by cout, VLOG(1)

> how to get the mesos-containerizer log-info
> ---
>
> Key: MESOS-7885
> URL: https://issues.apache.org/jira/browse/MESOS-7885
> Project: Mesos
>  Issue Type: Bug
>  Components: executor
>Affects Versions: 1.2.0
>Reporter: y123456yz
>
> how to get the mesos-containerizer log-info
> I don't find the log info of mesos-containerizer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7885) how to get the mesos-containerizer log-info

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7885:
--

[~jvanremoortere]

can you help me, I want to debug the  mesos-containerizer ,bug I can,t get the 
log of mesos-containerizer

> how to get the mesos-containerizer log-info
> ---
>
> Key: MESOS-7885
> URL: https://issues.apache.org/jira/browse/MESOS-7885
> Project: Mesos
>  Issue Type: Bug
>  Components: executor
>Affects Versions: 1.2.0
>Reporter: y123456yz
>
> how to get the mesos-containerizer log-info
> I don't find the log info of mesos-containerizer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-7813:
-
Comment: was deleted

(was: [~jvanremoortere]

thanks very much.

1. 
my lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started by command lines, not through systemd 
service.

whther I should start my Executor and lxc by systemd service(add 
delegate=true)? now, I start them by command lines, not by systemd service, as 
following:
/usr/bin/my-Executor -f xxx -d &
/usr/bin/lxc-start -f config -n xxx &

if must add "delegate=true", how to add "delegate=true" when I start my 
Executor  and lxc-start by command lines.


2.
there have another problem, sometimes, when I restart mesos service, the lxc 
container stoped automaticly, I don't known what happen.

when I run "systemctl restart mesos-slave", mesos-slave send KILL signal to 
my-Executor, then all the lxc-start process also receive KILL signal. 
my-Executor run lxc-start by " CmdUtil.exec("lxc-start -f config -n xxx -d ")

thanks again, Joris Van Remoortere
)

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MESOS-7885) how to get the mesos-containerizer log-info

[y123456yz (JIRA)]

y123456yz created MESOS-7885:


 Summary: how to get the mesos-containerizer log-info
 Key: MESOS-7885
 URL: https://issues.apache.org/jira/browse/MESOS-7885
 Project: Mesos
  Issue Type: Bug
  Components: executor
Affects Versions: 1.2.0
Reporter: y123456yz


how to get the mesos-containerizer log-info
I don't find the log info of mesos-containerizer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7855) re-compile the mesos src-code is too slow,when I re-compile the src code, it took half hour.

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7855:
--

[~kaysoky]

I only add a printf in function " Future 
MesosContainerizerProcess::_launch",  add following:
LOG(INFO) << "containerizer end"; //yang add
  

then I enter src:
cd mesos-1.2.0
cd src
make -j 8
I wait half hour.




[root@bogon mesos-1.2.0/src]# top
top - 14:22:06 up 31 days, 18:38,  3 users,  load average: 6.88, 4.71, 2.29
Tasks: 270 total,   1 running, 269 sleeping,   0 stopped,   0 zombie
%Cpu0  :  0.7 us,  0.7 sy,  0.0 ni, 39.7 id, 58.8 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu1  :  0.7 us,  0.0 sy,  0.0 ni, 30.9 id, 68.4 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu2  :  0.4 us,  0.0 sy,  0.0 ni, 90.4 id,  9.2 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu3  :  0.4 us,  0.7 sy,  0.0 ni,  3.3 id, 95.6 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu4  : 12.8 us,  2.2 sy,  0.0 ni, 81.3 id,  3.7 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu5  : 18.4 us,  2.6 sy,  0.0 ni, 72.8 id,  6.2 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu6  :  2.2 us,  2.2 sy,  0.0 ni,  0.0 id, 95.5 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu7  :  0.4 us,  0.4 sy,  0.0 ni, 63.0 id, 36.3 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  7939116 total,  6464936 free,  1193584 used,   280596 buff/cache
KiB Swap:  8126460 total,  6384936 free,  1741524 used.  6416940 avail Mem 

> re-compile the mesos src-code is too slow,when I re-compile the src code, it 
> took  half hour. 
> --
>
> Key: MESOS-7855
> URL: https://issues.apache.org/jira/browse/MESOS-7855
> Project: Mesos
>  Issue Type: Bug
>  Components: cmake
>Affects Versions: 1.2.0
>Reporter: y123456yz
>
> re-compile the mesos src-code is too slow
> I only add a line of printf. bug when I re-compile the src code, it took  
> half hour. 
> my god.
> how to speed up the src-compile.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MESOS-7855) re-compile the mesos src-code is too slow,when I re-compile the src code, it took half hour.

[y123456yz (JIRA)]

y123456yz created MESOS-7855:


 Summary: re-compile the mesos src-code is too slow,when I 
re-compile the src code, it took  half hour. 
 Key: MESOS-7855
 URL: https://issues.apache.org/jira/browse/MESOS-7855
 Project: Mesos
  Issue Type: Bug
  Components: cmake
Affects Versions: 1.2.0
Reporter: y123456yz


re-compile the mesos src-code is too slow

I only add a line of printf. bug when I re-compile the src code, it took  half 
hour. 
my god.
how to speed up the src-compile.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7846) when I upgrade my executor, mesos-slave kill all my lxc tasks, why? how to deal this porblem.

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7846:
--

add checkpoint can resolve this problem.

> when I upgrade my executor, mesos-slave kill all my lxc tasks, why? how to 
> deal this porblem.
> -
>
> Key: MESOS-7846
> URL: https://issues.apache.org/jira/browse/MESOS-7846
> Project: Mesos
>  Issue Type: Bug
>  Components: cgroups, executor
>Affects Versions: 1.1.0
>Reporter: y123456yz
>
> when I upgrade my executor, mesos-slave kill all my lxc tasks, why? how to 
> deal this porblem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MESOS-7846) when I upgrade my executor, mesos-slave kill all my lxc tasks, why? how to deal this porblem.

[y123456yz (JIRA)]

y123456yz created MESOS-7846:


 Summary: when I upgrade my executor, mesos-slave kill all my lxc 
tasks, why? how to deal this porblem.
 Key: MESOS-7846
 URL: https://issues.apache.org/jira/browse/MESOS-7846
 Project: Mesos
  Issue Type: Bug
  Components: cgroups, executor
Affects Versions: 1.1.0
Reporter: y123456yz


when I upgrade my executor, mesos-slave kill all my lxc tasks, why? how to deal 
this porblem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MESOS-7844) cordump when I run test-executor

[y123456yz (JIRA)]

y123456yz created MESOS-7844:


 Summary: cordump when I run test-executor
 Key: MESOS-7844
 URL: https://issues.apache.org/jira/browse/MESOS-7844
 Project: Mesos
  Issue Type: Bug
  Components: executor, test
Affects Versions: 1.2.0
 Environment: cordump when I run test-executor 
Reporter: y123456yz


[root@bogon src]# ps -ef | grep mesos-
root 27799  7928  0 14:19 pts/200:00:00 grep --color=auto mesos-
root 28975  7928  1 10:52 pts/200:02:49 
/home/xxx/mesos-1.2.0/src/.libs/lt-mesos-master --ip=172.23.133.32 
--work_dir=./work-mesos/
root 29044  7928  1 10:52 pts/200:02:35 
/home/xxx/mesos-1.2.0/src/.libs/lt-mesos-agent --master=172.23.133.32:5050 
--work_dir=./work-mesos/
[root@bogon src]# 
[root@bogon src]# 
[root@bogon src]# 
[root@bogon src]# export MESOS_SLAVE_PID=29044
[root@bogon src]# ./test-executor 
yang test 1
F0801 14:19:57.398921 27800 exec.cpp:738] Check failed: slave Cannot parse 
MESOS_SLAVE_PID '29044'
*** Check failure stack trace: ***
@ 0x7fad6d934e06  google::LogMessage::Fail()
@ 0x7fad6d934d65  google::LogMessage::SendToLog()
@ 0x7fad6d934776  google::LogMessage::Flush()
@ 0x7fad6d9374aa  google::LogMessageFatal::~LogMessageFatal()
@ 0x7fad6c2a0d11  mesos::MesosExecutorDriver::start()
@ 0x7fad6c2a216b  mesos::MesosExecutorDriver::run()
@ 0x7fad6f13bc49  main
@ 0x7fad67489b35  __libc_start_main
@ 0x7fad6f13bad9  (unknown)
已放弃(吐核)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-4727) Core dump while running python test framework test-executor

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-4727:
--

I have the same problem。
+1

[~vinodkone]

[root@bogon src]# ps -ef | grep mesos-
root 27799  7928  0 14:19 pts/200:00:00 grep --color=auto mesos-
root 28975  7928  1 10:52 pts/200:02:49 
/home/xxx/mesos-1.2.0/src/.libs/lt-mesos-master --ip=172.23.133.32 
--work_dir=./work-mesos/
root 29044  7928  1 10:52 pts/200:02:35 
/home/xxx/mesos-1.2.0/src/.libs/lt-mesos-agent --master=172.23.133.32:5050 
--work_dir=./work-mesos/
[root@bogon src]# 
[root@bogon src]# 
[root@bogon src]# 
[root@bogon src]# export MESOS_SLAVE_PID=29044
[root@bogon src]# ./test-executor 
yang test 1
F0801 14:19:57.398921 27800 exec.cpp:738] Check failed: slave Cannot parse 
MESOS_SLAVE_PID '29044'
*** Check failure stack trace: ***
@ 0x7fad6d934e06  google::LogMessage::Fail()
@ 0x7fad6d934d65  google::LogMessage::SendToLog()
@ 0x7fad6d934776  google::LogMessage::Flush()
@ 0x7fad6d9374aa  google::LogMessageFatal::~LogMessageFatal()
@ 0x7fad6c2a0d11  mesos::MesosExecutorDriver::start()
@ 0x7fad6c2a216b  mesos::MesosExecutorDriver::run()
@ 0x7fad6f13bc49  main
@ 0x7fad67489b35  __libc_start_main
@ 0x7fad6f13bad9  (unknown)
已放弃(吐核)
[root@bogon src]# 



> Core dump while running python test framework test-executor
> ---
>
> Key: MESOS-4727
> URL: https://issues.apache.org/jira/browse/MESOS-4727
> Project: Mesos
>  Issue Type: Bug
>  Components: test
> Environment: OSX 10.11.3, python version: 2.7.10
>Reporter: Marc Koderer
>
> Steps to reproduce:
> --
> Follow the Getting started section in documentation:
> 1.) ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos
> 2.) ./bin/mesos-slave.sh --master=127.0.0.1:5050
> 3.) ./src/examples/python/test-framework 127.0.0.1:5050
> 4.) start test-executor
> Result:
> Starting executor
> F0220 19:28:51.883116 1957933056 exec.cpp:653] Check failed: slave Cannot 
> parse MESOS_SLAVE_PID '18454'
> *** Check failure stack trace: ***
> @0x1098c910a  google::LogMessage::Fail()
> @0x1098c8097  google::LogMessage::SendToLog()
> @0x1098c8dba  google::LogMessage::Flush()
> @0x1098cfc28  google::LogMessageFatal::~LogMessageFatal()
> @0x1098c9545  google::LogMessageFatal::~LogMessageFatal()
> @0x10738d7ad  mesos::MesosExecutorDriver::start()
> @0x10738ef7a  mesos::MesosExecutorDriver::run()
> @0x1071969d1  mesos::python::MesosExecutorDriverImpl_run()
> @0x106779001  PyEval_EvalFrameEx
> @0x106775715  PyEval_EvalCodeEx
> @0x1067750e0  PyEval_EvalCode
> @0x106795242  run_mod
> @0x1067952e5  PyRun_FileExFlags
> @0x106794e34  PyRun_SimpleFileExFlags
> @0x1067a6731  Py_Main
> @ 0x7fff852985ad  start
>   Abort trap: 6
> Core dump trace:
> $ lldb -c /cores/core.19339
> (lldb) pla sta
>   Platform: host
> Triple: x86_64-apple-macosx
> OS Version: 10.11.3 (15D21)
> Kernel: Darwin Kernel Version 15.3.0: Thu Dec 10 18:40:58 PST 2015; 
> root:xnu-3248.30.4~1/RELEASE_X86_64
>   Hostname: 127.0.0.1
> WorkingDir: /Users/marc/git/mesos/build/src/examples/python
> (lldb) bt
> * thread #1: tid = 0x, 0x7fff88d51002 
> libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP
>   * frame #0: 0x7fff88d51002 libsystem_kernel.dylib`__pthread_kill + 10
> frame #1: 0x7fff95d575c5 libsystem_pthread.dylib`pthread_kill + 90
> frame #2: 0x7fff847916e7 libsystem_c.dylib`abort + 129
> frame #3: 0x00010719de86 _mesos.so`::DumpStackTraceAndExit() + 118 at 
> utilities.cc:147
> frame #4: 0x00010718910a _mesos.so`::Fail() + 10 at logging.cc:1458
> frame #5: 0x000107188097 _mesos.so`::SendToLog() + 1207 at 
> logging.cc:1412
> frame #6: 0x000107188dba _mesos.so`::Flush() + 378 at logging.cc:1281
> frame #7: 0x00010718fc28 _mesos.so`::~LogMessageFatal() + 24 at 
> logging.cc:1984
> frame #8: 0x000107189545 _mesos.so`::~LogMessageFatal() + 21 at 
> logging.cc:1983
> frame #9: 0x000104c4d7ad _mesos.so`::start() + 3005 at exec.cpp:653
> frame #10: 0x000104c4ef7a _mesos.so`::run() + 26 at exec.cpp:799
> frame #11: 0x000104a569d1 _mesos.so`::MesosExecutorDriverImpl_run() + 
> 97 at mesos_executor_driver_impl.cpp:296
> frame #12: 0x00010403f001 Python`PyEval_EvalFrameEx + 14074
> frame #13: 0x00010403b715 Python`PyEval_EvalCodeEx + 1583
> frame #14: 0x00010403b0e0 Python`PyEval_EvalCode + 54
> frame #15: 0x

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/27/17 10:31 AM:


[~jvanremoortere]

thanks very much.

1. 
my lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started by command lines, not through systemd 
service.

whther I should start my Executor and lxc by systemd service(add 
delegate=true)? now, I start them by command lines, not by systemd service, as 
following:
/usr/bin/my-Executor -f xxx -d &
/usr/bin/lxc-start -f config -n xxx &

if must add "delegate=true", how to add "delegate=true" when I start my 
Executor  and lxc-start by command lines.


2.
there have another problem, sometimes, when I restart mesos service, the lxc 
container stoped automaticly, I don't known what happen.

when I run "systemctl restart mesos-slave", mesos-slave send KILL signal to 
my-Executor, then all the lxc-start process also receive KILL signal. 
my-Executor run lxc-start by " CmdUtil.exec("lxc-start -f config -n xxx -d ")

thanks again, Joris Van Remoortere



was (Author: y123456yz):
[~jvanremoortere]

thanks very much.

1. 
my lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started by command lines, not through systemd 
service.

whther I should start my Executor and lxc by systemd service(add 
delegate=true)? now, I start them by command lines, not by systemd service, as 
following:
/usr/bin/my-Executor -f xxx -d &
/usr/bin/lxc-start -f config -n xxx &

if must add "delegate=true", how to add "delegate=true" when I start my 
Executor  and lxc-start by command lines.


2.
there have another problem, sometimes, when I restart mesos service, the lxc 
container stoped automaticly, I don't known what happen.

thanks again, Joris Van Remoortere


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/27/17 2:39 AM:
---

[~jvanremoortere]

thanks very much.

1. 
my lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started by command lines, not through systemd 
service.

whther I should start my Executor and lxc by systemd service(add 
delegate=true)? now, I start them by command lines, not by systemd service, as 
following:
/usr/bin/my-Executor -f xxx -d &
/usr/bin/lxc-start -f config -n xxx &

if must add "delegate=true", how to add "delegate=true" when I start my 
Executor  and lxc-start by command lines.


2.
there have another problem, sometimes, when I restart mesos service, the lxc 
container stoped automaticly, I don't known what happen.

thanks again, Joris Van Remoortere



was (Author: y123456yz):
[~jvanremoortere]

thanks very much.

1. 
my lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started by command lines, not through systemd 
service.

whther I should start my Executor and lxc by systemd service(add 
delegate=true)? now, I start them by command lines, not by systemd service, as 
following:
/usr/bin/my-Executor -f xxx -d &
/usr/bin/lxc-start -f config -n xxx &

if must add "delegate=true", how to add "delegate=true" when I start my 
Executor  and lxc-start by command lines.


2.
there have another problem, sometimes, when I restart mesos service, the lxc 
container stoped automaticly.

thanks again, Joris Van Remoortere


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/27/17 2:37 AM:
---

[~jvanremoortere]

thanks very much.

1. 
my lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started by command lines, not through systemd 
service.

whther I should start my Executor and lxc by systemd service(add 
delegate=true)? now, I start them by command lines, not by systemd service, as 
following:
/usr/bin/my-Executor -f xxx -d &
/usr/bin/lxc-start -f config -n xxx &

if must add "delegate=true", how to add "delegate=true" when I start my 
Executor  and lxc-start by command lines.


2.
there have another problem, sometimes, when I restart mesos service, the lxc 
container stoped automaticly.

thanks again, Joris Van Remoortere



was (Author: y123456yz):
[~jvanremoortere]

thanks very much.

there have another problem, sometimes, when I restart mesos service, the lxc 
container(lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started not through systemd service) stoped 
automaticly.

whther I should start my Executor and lxc by systemd service(add 
delegate=true)? now, I start them by command lines, not by systemd service, as 
following:
/usr/bin/my-Executor -f xxx -d &
/usr/bin/lxc-start -f config -n xxx &

thanks again, Joris Van Remoortere


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/27/17 2:24 AM:
---

[~jvanremoortere]

thanks very much.

there have another problem, sometimes, when I restart mesos service, the lxc 
container(lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started not through systemd service) stoped 
automaticly.

whther I should start my Executor and lxc by systemd service(add 
delegate=true)? now, I start them by command lines, not by systemd service, as 
following:
/usr/bin/my-Executor -f xxx -d &
/usr/bin/lxc-start -f config -n xxx &

thanks again, Joris Van Remoortere



was (Author: y123456yz):
[~jvanremoortere]

thanks very much.

there have another problem, sometimes, when I restart mesos service, the lxc 
container(lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started not through systemd service) stoped 
automaticly.

whther I should start my Executor and lxc by systemd service? now, I start them 
by command lines, as following:
/usr/bin/my-Executor -f xxx -d
/usr/bin/lxc-start -f config -n xxx

thanks again, Joris Van Remoortere


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/27/17 2:21 AM:
---

[~jvanremoortere]

thanks very much.

there have another problem, sometimes, when I restart mesos service, the lxc 
container(lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started not through systemd service) stoped 
automaticly.

whther I should start my Executor and lxc by systemd service? now, I start them 
by command lines, as following:
/usr/bin/my-Executor -f xxx -d
/usr/bin/lxc-start -f config -n xxx

thanks again, Joris Van Remoortere



was (Author: y123456yz):
[~jvanremoortere]

thanks very much.

there have another problem, sometimes, when I restart mesos service, the lxc 
container(lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started not through systemd service) stoped 
automaticly.

wheher I should start my Executor and lxc by systemd service? now, I start them 
by command lines, as following:
/usr/bin/my-Executor -f xxx -d
/usr/bin/lxc-start -f config -n xxx

thanks again, Joris Van Remoortere


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/27/17 2:17 AM:
---

[~jvanremoortere]

thanks very much.

there have another problem, sometimes, when I restart mesos service, the lxc 
container(lxc-start is started by my Executor, lxc-start running 
with"/usr/bin/lxc-start -f /xxx/config -n xxx",  Executor running with 
"/usr/bin/Executor  ", they started not through systemd service) stoped 
automaticly.

wheher I should start my Executor and lxc by systemd service? now, I start them 
by command lines, as following:
/usr/bin/my-Executor -f xxx -d
/usr/bin/lxc-start -f config -n xxx

thanks again, Joris Van Remoortere



was (Author: y123456yz):
[~jvanremoortere]

thanks very much.

there have another problem, sometimes, when I restart mesos service, the lxc 
container(lxc.service not contain "delegate=true") stoped automaticly.
maybe the systemd kill my lxc-start process?

thanks again, Joris Van Remoortere


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7813:
--

[~jvanremoortere]

thanks very much.

there have another problem, sometimes, when I restart mesos service, the lxc 
container(lxc.service not contain "delegate=true") stoped automaticly.
maybe the systemd kill my lxc-start process?

thanks again, Joris Van Remoortere


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-7813:
-
Comment: was deleted

(was: [~jvanremoortere]
I see you Website-link, but I still  don't understand who change the 
file(/proc/pid/cgroup) ,I never restart the lxc and mesos-slave.
You mean that systemd change the cgroup tasks?  why systemd change the cgroup 
info when lxc is running?)

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (MESOS-3009) Reproduce systemd cgroup behavior

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-3009:
-
Comment: was deleted

(was: when Delegate=false, restart result:

[root@bogon xxx]# cat /etc/systemd/system/lxc.service
[Unit]
Description=LXC Container Initialization and Autoboot Code
After=network.target lxc-net.service
Wants=lxc-net.service
Documentation=man:lxc-autostart man:lxc

[Service]
Delegate=false//Delegate=false
Type=oneshot
RemainAfterExit=yes
ExecStart= /usr/bin/lxc-start -f /home/xxx/lxc.conf3 -n yyz-test -d -o 
/home/xxx/yyzlxc.log
ExecStop=/usr/bin/lxc-stop -n yyz-test

[Install]
WantedBy=multi-user.target

[root@bogon xxx]# systemctl daemon-reload
[root@bogon xxx]# systemctl restart lxc

[root@bogon xxx]# cat /proc/23340/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-3
10:cpuset:/lxc/yyz-test-3
9:perf_event:/lxc/yyz-test-3
8:memory:/lxc/yyz-test-3
7:blkio:/lxc/yyz-test-3
6:freezer:/lxc/yyz-test-3
5:devices:/lxc/yyz-test-3
4:net_prio,net_cls:/lxc/yyz-test-3
3:pids:/lxc/yyz-test-3
2:hugetlb:/lxc/yyz-test-3
1:name=systemd:/lxc/yyz-test-3


[root@bogon xxx]#  echo 23340 > /sys/fs/cgroup/memory/user.slice/tasks 
[root@bogon xxx]# echo 23340 > /sys/fs/cgroup/blkio/user.slice/tasks 

[root@bogon xxx]# cat /proc/23340/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-3
10:cpuset:/lxc/yyz-test-3
9:perf_event:/lxc/yyz-test-3
8:memory:/user.slice
7:blkio:/user.slice
6:freezer:/lxc/yyz-test-3
5:devices:/lxc/yyz-test-3
4:net_prio,net_cls:/lxc/yyz-test-3
3:pids:/lxc/yyz-test-3
2:hugetlb:/lxc/yyz-test-3
1:name=systemd:/lxc/yyz-test-3

[root@bogon xxx]# systemctl restart lxc
[root@bogon xxx]# 
[root@bogon xxx]# ps -ef | grep init
root 23643 23638  0 17:49 ?00:00:00 /sbin/init
root 23859 15894  0 17:50 pts/200:00:00 grep --color=auto init
[root@bogon xxx]# cat /proc/23643/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-3
10:cpuset:/lxc/yyz-test-3
9:perf_event:/lxc/yyz-test-3
8:memory:/lxc/yyz-test-3
7:blkio:/lxc/yyz-test-3
6:freezer:/lxc/yyz-test-3
5:devices:/lxc/yyz-test-3
4:net_prio,net_cls:/lxc/yyz-test-3
3:pids:/lxc/yyz-test-3
2:hugetlb:/lxc/yyz-test-3
1:name=systemd:/lxc/yyz-test-3
[root@bogon xxx]# 

)

> Reproduce systemd cgroup behavior 
> --
>
> Key: MESOS-3009
> URL: https://issues.apache.org/jira/browse/MESOS-3009
> Project: Mesos
>  Issue Type: Task
>Reporter: Artem Harutyunyan
>Assignee: Joris Van Remoortere
>  Labels: mesosphere
>
> It has been noticed before that systemd reorganizes cgroup hierarchy created 
> by mesos slave. Because of this mesos is no longer able to find the cgroup, 
> and there is also a chance of undoing the isolation that mesos slave puts in 
> place. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (MESOS-3009) Reproduce systemd cgroup behavior

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-3009:
-
Comment: was deleted

(was: [~jvanremoortere]

my test result is that no matter "delegate=true" or "delegate=false", the 
result is same.
what's the real effect of “delegate=true“?

maybe my Understand is wrong, can you tell me the real diffrence of 
"delegate=true" and"delegate=false")

> Reproduce systemd cgroup behavior 
> --
>
> Key: MESOS-3009
> URL: https://issues.apache.org/jira/browse/MESOS-3009
> Project: Mesos
>  Issue Type: Task
>Reporter: Artem Harutyunyan
>Assignee: Joris Van Remoortere
>  Labels: mesosphere
>
> It has been noticed before that systemd reorganizes cgroup hierarchy created 
> by mesos slave. Because of this mesos is no longer able to find the cgroup, 
> and there is also a chance of undoing the isolation that mesos slave puts in 
> place. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (MESOS-3009) Reproduce systemd cgroup behavior

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-3009:
-
Comment: was deleted

(was: when Delegate=true, restart result:

[root@bogon xxx]# cat /etc/systemd/system/lxc.service
[Unit]
Description=LXC Container Initialization and Autoboot Code
After=network.target lxc-net.service
Wants=lxc-net.service
Documentation=man:lxc-autostart man:lxc
 
[Service]
Delegate=yes  //here  Delegate=yes  
Type=oneshot
RemainAfterExit=yes
ExecStart= /usr/bin/lxc-start -f /home/xxx/lxc.conf3 -n yyz-test -d -o 
/home/xxx/yyzlxc.log
ExecStop=/usr/bin/lxc-stop -n yyz-test 
 
[Install]
WantedBy=multi-user.target

[root@bogon xxx]# 
[root@bogon xxx]# cat /proc/21640/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-2
10:cpuset:/lxc/yyz-test-2
9:perf_event:/lxc/yyz-test-2
8:memory:/lxc/yyz-test-2
7:blkio:/lxc/yyz-test-2
6:freezer:/lxc/yyz-test-2
5:devices:/lxc/yyz-test-2
4:net_prio,net_cls:/lxc/yyz-test-2
3:pids:/lxc/yyz-test-2
2:hugetlb:/lxc/yyz-test-2
1:name=systemd:/lxc/yyz-test-2
[root@bogon xxx]# 
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/
blkio/cpuacct/  cpuset/   freezer/  memory/ 
  net_cls,net_prio/ perf_event/   systemd/  
cpu/  cpu,cpuacct/  devices/  hugetlb/  
net_cls/  net_prio/ pids/ 
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/memory/user.slice/tasks   
   
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/blkio/user.slice/tasks 
[root@bogon xxx]# cat /proc/21640/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-2
10:cpuset:/lxc/yyz-test-2
9:perf_event:/lxc/yyz-test-2
8:memory:/user.slice//here change
7:blkio:/user.slice //here change
6:freezer:/lxc/yyz-test-2
5:devices:/lxc/yyz-test-2
4:net_prio,net_cls:/lxc/yyz-test-2
3:pids:/lxc/yyz-test-2
2:hugetlb:/lxc/yyz-test-2
1:name=systemd:/lxc/yyz-test-2



[root@bogon ]# systemctl restart lxc
//here restart
[root@bogon yangyazhou]# ps -ef |grep init
root 23340 23335  0 17:48 ?00:00:00 /sbin/init
root 23533 15894  0 17:48 pts/200:00:00 grep --color=auto init
[root@bogon yangyazhou]# cat /proc/23340/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-3
10:cpuset:/lxc/yyz-test-3
9:perf_event:/lxc/yyz-test-3
8:memory:/lxc/yyz-test-3
7:blkio:/lxc/yyz-test-3
6:freezer:/lxc/yyz-test-3
5:devices:/lxc/yyz-test-3
4:net_prio,net_cls:/lxc/yyz-test-3
3:pids:/lxc/yyz-test-3
2:hugetlb:/lxc/yyz-test-3
1:name=systemd:/lxc/yyz-test-3

)

> Reproduce systemd cgroup behavior 
> --
>
> Key: MESOS-3009
> URL: https://issues.apache.org/jira/browse/MESOS-3009
> Project: Mesos
>  Issue Type: Task
>Reporter: Artem Harutyunyan
>Assignee: Joris Van Remoortere
>  Labels: mesosphere
>
> It has been noticed before that systemd reorganizes cgroup hierarchy created 
> by mesos slave. Because of this mesos is no longer able to find the cgroup, 
> and there is also a chance of undoing the isolation that mesos slave puts in 
> place. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-7813:
-
Comment: was deleted

(was: configure as following:

$ cat /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target

[Service]
ExecStart=/usr/bin/mesos-init-wrapper slave
KillMode=process
Restart=always
RestartSec=20
LimitNOFILE=16384
CPUAccounting=true
MemoryAccounting=true

[Install]
WantedBy=multi-user.target)

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-7813:
-
Comment: was deleted

(was: [~haosdent huang]
[~jvanremoortere]
[~jvanremoortere]
[~hartem]

can you help me , what happen for this, what's the reason. 
thans.


some lxc that Manually created by me(not through mesos) also have the problem, 
I don,t know who change this.

thans.)

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-7813:
-
Comment: was deleted

(was:  "delegate=true" can change this problem ?
)

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-3009) Reproduce systemd cgroup behavior

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-3009 at 7/22/17 10:06 AM:


when Delegate=true, restart result:

[root@bogon xxx]# cat /etc/systemd/system/lxc.service
[Unit]
Description=LXC Container Initialization and Autoboot Code
After=network.target lxc-net.service
Wants=lxc-net.service
Documentation=man:lxc-autostart man:lxc
 
[Service]
Delegate=yes  //here  Delegate=yes  
Type=oneshot
RemainAfterExit=yes
ExecStart= /usr/bin/lxc-start -f /home/xxx/lxc.conf3 -n yyz-test -d -o 
/home/xxx/yyzlxc.log
ExecStop=/usr/bin/lxc-stop -n yyz-test 
 
[Install]
WantedBy=multi-user.target

[root@bogon xxx]# 
[root@bogon xxx]# cat /proc/21640/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-2
10:cpuset:/lxc/yyz-test-2
9:perf_event:/lxc/yyz-test-2
8:memory:/lxc/yyz-test-2
7:blkio:/lxc/yyz-test-2
6:freezer:/lxc/yyz-test-2
5:devices:/lxc/yyz-test-2
4:net_prio,net_cls:/lxc/yyz-test-2
3:pids:/lxc/yyz-test-2
2:hugetlb:/lxc/yyz-test-2
1:name=systemd:/lxc/yyz-test-2
[root@bogon xxx]# 
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/
blkio/cpuacct/  cpuset/   freezer/  memory/ 
  net_cls,net_prio/ perf_event/   systemd/  
cpu/  cpu,cpuacct/  devices/  hugetlb/  
net_cls/  net_prio/ pids/ 
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/memory/user.slice/tasks   
   
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/blkio/user.slice/tasks 
[root@bogon xxx]# cat /proc/21640/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-2
10:cpuset:/lxc/yyz-test-2
9:perf_event:/lxc/yyz-test-2
8:memory:/user.slice//here change
7:blkio:/user.slice //here change
6:freezer:/lxc/yyz-test-2
5:devices:/lxc/yyz-test-2
4:net_prio,net_cls:/lxc/yyz-test-2
3:pids:/lxc/yyz-test-2
2:hugetlb:/lxc/yyz-test-2
1:name=systemd:/lxc/yyz-test-2



[root@bogon ]# systemctl restart lxc
//here restart
[root@bogon yangyazhou]# ps -ef |grep init
root 23340 23335  0 17:48 ?00:00:00 /sbin/init
root 23533 15894  0 17:48 pts/200:00:00 grep --color=auto init
[root@bogon yangyazhou]# cat /proc/23340/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-3
10:cpuset:/lxc/yyz-test-3
9:perf_event:/lxc/yyz-test-3
8:memory:/lxc/yyz-test-3
7:blkio:/lxc/yyz-test-3
6:freezer:/lxc/yyz-test-3
5:devices:/lxc/yyz-test-3
4:net_prio,net_cls:/lxc/yyz-test-3
3:pids:/lxc/yyz-test-3
2:hugetlb:/lxc/yyz-test-3
1:name=systemd:/lxc/yyz-test-3




was (Author: y123456yz):
when Delegate=true, restart result:

[root@bogon xxx]# cat /etc/systemd/system/lxc.service
[Unit]
Description=LXC Container Initialization and Autoboot Code
After=network.target lxc-net.service
Wants=lxc-net.service
Documentation=man:lxc-autostart man:lxc
 
[Service]
Delegate=yes   //here  Delegate=yes  
Type=oneshot
RemainAfterExit=yes
ExecStart= /usr/bin/lxc-start -f /home/xxx/lxc.conf3 -n yyz-test -d -o 
/home/xxx/yyzlxc.log
ExecStop=/usr/bin/lxc-stop -n yyz-test 
 
[Install]
WantedBy=multi-user.target

[root@bogon xxx]# 
[root@bogon xxx]# cat /proc/21640/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-2
10:cpuset:/lxc/yyz-test-2
9:perf_event:/lxc/yyz-test-2
8:memory:/lxc/yyz-test-2
7:blkio:/lxc/yyz-test-2
6:freezer:/lxc/yyz-test-2
5:devices:/lxc/yyz-test-2
4:net_prio,net_cls:/lxc/yyz-test-2
3:pids:/lxc/yyz-test-2
2:hugetlb:/lxc/yyz-test-2
1:name=systemd:/lxc/yyz-test-2
[root@bogon xxx]# 
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/
blkio/cpuacct/  cpuset/   freezer/  memory/ 
  net_cls,net_prio/ perf_event/   systemd/  
cpu/  cpu,cpuacct/  devices/  hugetlb/  
net_cls/  net_prio/ pids/ 
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/memory/user.slice/tasks   
   
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/blkio/user.slice/tasks 
[root@bogon xxx]# cat /proc/21640/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-2
10:cpuset:/lxc/yyz-test-2
9:perf_event:/lxc/yyz-test-2
8:memory:/user.slice//here change
7:blkio:/user.slice //here change
6:freezer:/lxc/yyz-test-2
5:devices:/lxc/yyz-test-2
4:net_prio,net_cls:/lxc/yyz-test-2
3:pids:/lxc/yyz-test-2
2:hugetlb:/lxc/yyz-test-2
1:name=systemd:/lxc/yyz-test-2



[root@bogon ]# systemctl restart lxc
//here restart
[root@bogon yangyazhou]# ps -ef |grep init
root 23340 23335  0 17:48 ?00:00:00 /sbin/init
root 23533 15894  0 17:48 pts/200:00:00 grep --color=auto init
[root@bogon yangyazhou]# cat /proc/23340/cgroup 
145:name=c

[jira] [Commented] (MESOS-3009) Reproduce systemd cgroup behavior

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-3009:
--

[~jvanremoortere]

my test result is that no matter "delegate=true" or "delegate=false", the 
result is same.
what's the real effect of “delegate=true“?

maybe my Understand is wrong, can you tell me the real diffrence of 
"delegate=true" and"delegate=false"

> Reproduce systemd cgroup behavior 
> --
>
> Key: MESOS-3009
> URL: https://issues.apache.org/jira/browse/MESOS-3009
> Project: Mesos
>  Issue Type: Task
>Reporter: Artem Harutyunyan
>Assignee: Joris Van Remoortere
>  Labels: mesosphere
>
> It has been noticed before that systemd reorganizes cgroup hierarchy created 
> by mesos slave. Because of this mesos is no longer able to find the cgroup, 
> and there is also a chance of undoing the isolation that mesos slave puts in 
> place. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-3009) Reproduce systemd cgroup behavior

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-3009:
--

when Delegate=false, restart result:

[root@bogon xxx]# cat /etc/systemd/system/lxc.service
[Unit]
Description=LXC Container Initialization and Autoboot Code
After=network.target lxc-net.service
Wants=lxc-net.service
Documentation=man:lxc-autostart man:lxc

[Service]
Delegate=false//Delegate=false
Type=oneshot
RemainAfterExit=yes
ExecStart= /usr/bin/lxc-start -f /home/xxx/lxc.conf3 -n yyz-test -d -o 
/home/xxx/yyzlxc.log
ExecStop=/usr/bin/lxc-stop -n yyz-test

[Install]
WantedBy=multi-user.target

[root@bogon xxx]# systemctl daemon-reload
[root@bogon xxx]# systemctl restart lxc

[root@bogon xxx]# cat /proc/23340/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-3
10:cpuset:/lxc/yyz-test-3
9:perf_event:/lxc/yyz-test-3
8:memory:/lxc/yyz-test-3
7:blkio:/lxc/yyz-test-3
6:freezer:/lxc/yyz-test-3
5:devices:/lxc/yyz-test-3
4:net_prio,net_cls:/lxc/yyz-test-3
3:pids:/lxc/yyz-test-3
2:hugetlb:/lxc/yyz-test-3
1:name=systemd:/lxc/yyz-test-3


[root@bogon xxx]#  echo 23340 > /sys/fs/cgroup/memory/user.slice/tasks 
[root@bogon xxx]# echo 23340 > /sys/fs/cgroup/blkio/user.slice/tasks 

[root@bogon xxx]# cat /proc/23340/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-3
10:cpuset:/lxc/yyz-test-3
9:perf_event:/lxc/yyz-test-3
8:memory:/user.slice
7:blkio:/user.slice
6:freezer:/lxc/yyz-test-3
5:devices:/lxc/yyz-test-3
4:net_prio,net_cls:/lxc/yyz-test-3
3:pids:/lxc/yyz-test-3
2:hugetlb:/lxc/yyz-test-3
1:name=systemd:/lxc/yyz-test-3

[root@bogon xxx]# systemctl restart lxc
[root@bogon xxx]# 
[root@bogon xxx]# ps -ef | grep init
root 23643 23638  0 17:49 ?00:00:00 /sbin/init
root 23859 15894  0 17:50 pts/200:00:00 grep --color=auto init
[root@bogon xxx]# cat /proc/23643/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-3
10:cpuset:/lxc/yyz-test-3
9:perf_event:/lxc/yyz-test-3
8:memory:/lxc/yyz-test-3
7:blkio:/lxc/yyz-test-3
6:freezer:/lxc/yyz-test-3
5:devices:/lxc/yyz-test-3
4:net_prio,net_cls:/lxc/yyz-test-3
3:pids:/lxc/yyz-test-3
2:hugetlb:/lxc/yyz-test-3
1:name=systemd:/lxc/yyz-test-3
[root@bogon xxx]# 



> Reproduce systemd cgroup behavior 
> --
>
> Key: MESOS-3009
> URL: https://issues.apache.org/jira/browse/MESOS-3009
> Project: Mesos
>  Issue Type: Task
>Reporter: Artem Harutyunyan
>Assignee: Joris Van Remoortere
>  Labels: mesosphere
>
> It has been noticed before that systemd reorganizes cgroup hierarchy created 
> by mesos slave. Because of this mesos is no longer able to find the cgroup, 
> and there is also a chance of undoing the isolation that mesos slave puts in 
> place. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-3009) Reproduce systemd cgroup behavior

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-3009:
--

when Delegate=true, restart result:

[root@bogon xxx]# cat /etc/systemd/system/lxc.service
[Unit]
Description=LXC Container Initialization and Autoboot Code
After=network.target lxc-net.service
Wants=lxc-net.service
Documentation=man:lxc-autostart man:lxc
 
[Service]
Delegate=yes   //here  Delegate=yes  
Type=oneshot
RemainAfterExit=yes
ExecStart= /usr/bin/lxc-start -f /home/xxx/lxc.conf3 -n yyz-test -d -o 
/home/xxx/yyzlxc.log
ExecStop=/usr/bin/lxc-stop -n yyz-test 
 
[Install]
WantedBy=multi-user.target

[root@bogon xxx]# 
[root@bogon xxx]# cat /proc/21640/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-2
10:cpuset:/lxc/yyz-test-2
9:perf_event:/lxc/yyz-test-2
8:memory:/lxc/yyz-test-2
7:blkio:/lxc/yyz-test-2
6:freezer:/lxc/yyz-test-2
5:devices:/lxc/yyz-test-2
4:net_prio,net_cls:/lxc/yyz-test-2
3:pids:/lxc/yyz-test-2
2:hugetlb:/lxc/yyz-test-2
1:name=systemd:/lxc/yyz-test-2
[root@bogon xxx]# 
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/
blkio/cpuacct/  cpuset/   freezer/  memory/ 
  net_cls,net_prio/ perf_event/   systemd/  
cpu/  cpu,cpuacct/  devices/  hugetlb/  
net_cls/  net_prio/ pids/ 
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/memory/user.slice/tasks   
   
[root@bogon xxx]# echo 21640 > /sys/fs/cgroup/blkio/user.slice/tasks 
[root@bogon xxx]# cat /proc/21640/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-2
10:cpuset:/lxc/yyz-test-2
9:perf_event:/lxc/yyz-test-2
8:memory:/user.slice//here change
7:blkio:/user.slice //here change
6:freezer:/lxc/yyz-test-2
5:devices:/lxc/yyz-test-2
4:net_prio,net_cls:/lxc/yyz-test-2
3:pids:/lxc/yyz-test-2
2:hugetlb:/lxc/yyz-test-2
1:name=systemd:/lxc/yyz-test-2



[root@bogon ]# systemctl restart lxc
//here restart
[root@bogon yangyazhou]# ps -ef |grep init
root 23340 23335  0 17:48 ?00:00:00 /sbin/init
root 23533 15894  0 17:48 pts/200:00:00 grep --color=auto init
[root@bogon yangyazhou]# cat /proc/23340/cgroup 
145:name=cgroup-yyztest:/
11:cpuacct,cpu:/lxc/yyz-test-3
10:cpuset:/lxc/yyz-test-3
9:perf_event:/lxc/yyz-test-3
8:memory:/lxc/yyz-test-3
7:blkio:/lxc/yyz-test-3
6:freezer:/lxc/yyz-test-3
5:devices:/lxc/yyz-test-3
4:net_prio,net_cls:/lxc/yyz-test-3
3:pids:/lxc/yyz-test-3
2:hugetlb:/lxc/yyz-test-3
1:name=systemd:/lxc/yyz-test-3



> Reproduce systemd cgroup behavior 
> --
>
> Key: MESOS-3009
> URL: https://issues.apache.org/jira/browse/MESOS-3009
> Project: Mesos
>  Issue Type: Task
>Reporter: Artem Harutyunyan
>Assignee: Joris Van Remoortere
>  Labels: mesosphere
>
> It has been noticed before that systemd reorganizes cgroup hierarchy created 
> by mesos slave. Because of this mesos is no longer able to find the cgroup, 
> and there is also a chance of undoing the isolation that mesos slave puts in 
> place. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/22/17 9:35 AM:
---

[~jvanremoortere]
I see you Website-link, but I still  don't understand who change the 
file(/proc/pid/cgroup) ,I never restart the lxc and mesos-slave.
You mean that systemd change the cgroup tasks?  why systemd change the cgroup 
info when lxc is running?


was (Author: y123456yz):
[~jvanremoortere]
I see you Website-link, but I still  don't understand who change the 
file(/proc/pid/cgroup) ,I never restart the lxc and mesos-slave.
You mean that systemd change the cgroup tasks?

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7813:
--

[~jvanremoortere]
I see you Website-link, but I still  don't understand who change the 
file(/proc/pid/cgroup) ,I never restart the lxc and mesos-slave.
You mean that systemd change the cgroup tasks?

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/22/17 9:06 AM:
---

 "delegate=true" can change this problem ?



was (Author: y123456yz):
I have resolve the problem by "delegate=true"


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/22/17 9:05 AM:
---

I have resolve the problem by "delegate=true"



was (Author: y123456yz):
I have resolve the problem by "delegate=true"

thanks

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/21/17 2:24 AM:
---

I have resolve the problem by "delegate=true"

thanks


was (Author: y123456yz):
[~jvanremoortere]
[~hartem]
[~jvanremoortere]
where the flowing config should be add to?
delegate=true

 cat /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target
[Service]
delegate=true // add here??


only add "delegate=true" to mesos-slave.service's [Service]? 


whether need to add "KillMode=control-group" to  mesos-slave.service's 
[Service]? 

thanks again!


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-7813:
-
Comment: was deleted

(was: [~jvanremoortere]

can you tell me that how to Check out the delegate flag in systemd?)

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7813:
--

[~jvanremoortere]

can you tell me that how to Check out the delegate flag in systemd?

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/20/17 7:19 AM:
---

[~jvanremoortere]
[~hartem]
[~jvanremoortere]
where the flowing config should be add to?
delegate=true

 cat /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target
[Service]
delegate=true // add here??


only add "delegate=true" to mesos-slave.service's [Service]? 


whether need to add "KillMode=control-group" to  mesos-slave.service's 
[Service]? 

thanks again!



was (Author: y123456yz):
[~jvanremoortere]
where the flowing config should be add to?
delegate=true

 cat /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target
[Service]
delegate=true // add here??


only add "delegate=true" to mesos-slave.service's [Service]? 


whether need to add "KillMode=control-group" to  mesos-slave.service's 
[Service]? 

thanks again!


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/20/17 5:07 AM:
---

[~jvanremoortere]
where the flowing config should be add to?
delegate=true

 cat /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target
[Service]
delegate=true // add here??


only add "delegate=true" to mesos-slave.service's [Service]? 


whether need to add "KillMode=control-group" to  mesos-slave.service's 
[Service]? 

thanks again!



was (Author: y123456yz):
[~jvanremoortere]
where the flowing config should be add to?
delegate=true

 cat /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target
[Service]
delegate=true   // add here??


only add "delegate=true" to mesos-slave.service's [Service]? 


whether need to add "KillMode=control-group" to  mesos-slave.service's 
[Service]? 

thanks again!


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7813:
--

[~jvanremoortere]
where the flowing config should be add to?
delegate=true

 cat /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target
[Service]
delegate=true   // add here??


only add "delegate=true" to mesos-slave.service's [Service]? 


whether need to add "KillMode=control-group" to  mesos-slave.service's 
[Service]? 

thanks again!


> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/20/17 3:36 AM:
---

last time, as following:
[xxx@fd-mesos-xxx~]$ cat /proc/30115/cgroup 
10:perf_event:/lxc/c8cef9e2ff114e429cb845559c4a0dff
9:cpuset:/lxc/c8cef9e2ff114e429cb845559c4a0dff
8:net_cls:/lxc/c8cef9e2ff114e429cb845559c4a0dff
7:devices:/lxc/c8cef9e2ff114e429cb845559c4a0dff
6:hugetlb:/lxc/c8cef9e2ff114e429cb845559c4a0dff
5:blkio:/lxc/c8cef9e2ff114e429cb845559c4a0dff
4:memory:/lxc/c8cef9e2ff114e429cb845559c4a0dff
3:cpuacct,cpu:/lxc/c8cef9e2ff114e429cb845559c4a0dff
2:freezer:/lxc/c8cef9e2ff114e429cb845559c4a0dff
1:name=systemd:/user.slice/user-52321.slice/session-128207.scope


After a period of time， changed as folloing:
[yangyazhou@fd-mesos-slave21 ~]$ cat /proc/30115/cgroup 
10:perf_event:/lxc/c8cef9e2ff114e429cb845559c4a0dff
9:cpuset:/lxc/c8cef9e2ff114e429cb845559c4a0dff
8:net_cls:/lxc/c8cef9e2ff114e429cb845559c4a0dff
7:devices:/user.slice
6:hugetlb:/lxc/c8cef9e2ff114e429cb845559c4a0dff
5:blkio:/user.slice
4:memory:/user.slice
3:cpuacct,cpu:/user.slice
2:freezer:/lxc/c8cef9e2ff114e429cb845559c4a0dff
1:name=systemd:/user.slice/user-52321.slice/session-128207.scope




systemd version:
[xxx~]$ rpm -qa | grep systemd
systemd-sysv-219-30.el7.x86_64
oci-systemd-hook-0.1.4-4.git41491a3.el7.x86_64
systemd-libs-219-30.el7.x86_64
systemd-219-30.el7.x86_64
systemd-devel-219-30.el7.x86_64
systemd-python-219-30.el7.x86_64


was (Author: y123456yz):
last time, as following:
[xxx@fd-mesos-xxx~]$ cat /proc/30115/cgroup 
10:perf_event:/lxc/c8cef9e2ff114e429cb845559c4a0dff
9:cpuset:/lxc/c8cef9e2ff114e429cb845559c4a0dff
8:net_cls:/lxc/c8cef9e2ff114e429cb845559c4a0dff
7:devices:/lxc/c8cef9e2ff114e429cb845559c4a0dff
6:hugetlb:/lxc/c8cef9e2ff114e429cb845559c4a0dff
5:blkio:/lxc/c8cef9e2ff114e429cb845559c4a0dff
4:memory:/lxc/c8cef9e2ff114e429cb845559c4a0dff
3:cpuacct,cpu:/lxc/c8cef9e2ff114e429cb845559c4a0dff
2:freezer:/lxc/c8cef9e2ff114e429cb845559c4a0dff
1:name=systemd:/user.slice/user-52321.slice/session-128207.scope


After a period of time， changed as folloing:
[yangyazhou@fd-mesos-slave21 ~]$ cat /proc/30115/cgroup 
10:perf_event:/lxc/c8cef9e2ff114e429cb845559c4a0dff
9:cpuset:/lxc/c8cef9e2ff114e429cb845559c4a0dff
8:net_cls:/lxc/c8cef9e2ff114e429cb845559c4a0dff
7:devices:/user.slice
6:hugetlb:/lxc/c8cef9e2ff114e429cb845559c4a0dff
5:blkio:/user.slice
4:memory:/user.slice
3:cpuacct,cpu:/user.slice
2:freezer:/lxc/c8cef9e2ff114e429cb845559c4a0dff
1:name=systemd:/user.slice/user-52321.slice/session-128207.scope

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz edited comment on MESOS-7813 at 7/20/17 3:07 AM:
---

configure as following:

$ cat /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target

[Service]
ExecStart=/usr/bin/mesos-init-wrapper slave
KillMode=process
Restart=always
RestartSec=20
LimitNOFILE=16384
CPUAccounting=true
MemoryAccounting=true

[Install]
WantedBy=multi-user.target


was (Author: y123456yz):
$ cat /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target

[Service]
ExecStart=/usr/bin/mesos-init-wrapper slave
KillMode=process
Restart=always
RestartSec=20
LimitNOFILE=16384
CPUAccounting=true
MemoryAccounting=true

[Install]
WantedBy=multi-user.target

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7813:
--

$ cat /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target

[Service]
ExecStart=/usr/bin/mesos-init-wrapper slave
KillMode=process
Restart=always
RestartSec=20
LimitNOFILE=16384
CPUAccounting=true
MemoryAccounting=true

[Install]
WantedBy=multi-user.target

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7813:
--

[~haosdent huang]
[~jvanremoortere]
[~jvanremoortere]
[~hartem]

can you help me , what happen for this, what's the reason. 
thans.


some lxc that Manually created by me(not through mesos) also have the problem, 
I don,t know who change this.

thans.

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-7813:
-
Component/s: framework
 executor
 agent

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

y123456yz updated MESOS-7813:
-
Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
GNU/Linux

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: agent, cgroups, executor, framework
> Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 
> GNU/Linux
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

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

y123456yz commented on MESOS-7813:
--

last time, as following:
[xxx@fd-mesos-xxx~]$ cat /proc/30115/cgroup 
10:perf_event:/lxc/c8cef9e2ff114e429cb845559c4a0dff
9:cpuset:/lxc/c8cef9e2ff114e429cb845559c4a0dff
8:net_cls:/lxc/c8cef9e2ff114e429cb845559c4a0dff
7:devices:/lxc/c8cef9e2ff114e429cb845559c4a0dff
6:hugetlb:/lxc/c8cef9e2ff114e429cb845559c4a0dff
5:blkio:/lxc/c8cef9e2ff114e429cb845559c4a0dff
4:memory:/lxc/c8cef9e2ff114e429cb845559c4a0dff
3:cpuacct,cpu:/lxc/c8cef9e2ff114e429cb845559c4a0dff
2:freezer:/lxc/c8cef9e2ff114e429cb845559c4a0dff
1:name=systemd:/user.slice/user-52321.slice/session-128207.scope


After a period of time， changed as folloing:
[yangyazhou@fd-mesos-slave21 ~]$ cat /proc/30115/cgroup 
10:perf_event:/lxc/c8cef9e2ff114e429cb845559c4a0dff
9:cpuset:/lxc/c8cef9e2ff114e429cb845559c4a0dff
8:net_cls:/lxc/c8cef9e2ff114e429cb845559c4a0dff
7:devices:/user.slice
6:hugetlb:/lxc/c8cef9e2ff114e429cb845559c4a0dff
5:blkio:/user.slice
4:memory:/user.slice
3:cpuacct,cpu:/user.slice
2:freezer:/lxc/c8cef9e2ff114e429cb845559c4a0dff
1:name=systemd:/user.slice/user-52321.slice/session-128207.scope

> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?
> --
>
> Key: MESOS-7813
> URL: https://issues.apache.org/jira/browse/MESOS-7813
> Project: Mesos
>  Issue Type: Bug
>  Components: cgroups
>Reporter: y123456yz
>
> when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
> devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why?

[y123456yz (JIRA)]

y123456yz created MESOS-7813:


 Summary: when lxc run after a period of time, the 
file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. 
why?
 Key: MESOS-7813
 URL: https://issues.apache.org/jira/browse/MESOS-7813
 Project: Mesos
  Issue Type: Bug
  Components: cgroups
Reporter: y123456yz


when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, 
devices,blkio,memory,cpuacct is changed. why?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)