cf-natali commented on pull request #388: URL: https://github.com/apache/mesos/pull/388#issuecomment-866194661
> > It happens in case of freeze timeout: https://github.com/apache/mesos/blob/master/src/linux/cgroups.cpp#L1423 > > The freeze is discarded, then it calls kill - which doesn't log anything - then it calls thaw. > > I see the timeout for freeze is 10 seconds (`FREEZE_RETRY_INTERVAL`), so if that occurs, there should be ~10s interval between the log messages `Freezing cgroup ...` and `Thawing cgroup ...`, but that's not the case in the log messages you posted: > > ``` > I0516 23:58:42.638830 466897 linux_launcher.cpp:606] Destroying cgroup '/sys/fs/cgroup/freezer/mesos_test_98d2814b-03ad-4c14-a3f9-832ab688e386/3139257f-4e7a-4828-9af4-75c867846558' > I0516 23:58:42.639083 466898 composing.cpp:343] Finished recovering all containerizers > I0516 23:58:42.639549 466898 cgroups.cpp:2934] Freezing cgroup /sys/fs/cgroup/freezer/mesos_test_98d2814b-03ad-4c14-a3f9-832ab688e386/3139257f-4e7a-4828-9af4-75c867846558 > I0516 23:58:42.714794 466899 cgroups.cpp:2952] Thawing cgroup /sys/fs/cgroup/freezer/mesos_test_98d2814b-03ad-4c14-a3f9-832ab688e386/3139257f-4e7a-4828-9af4-75c867846558 > ``` That's because the test uses `Clock::pause`, `Clock::advance` and `Clock::settle` to advance the time, hence the freeze timeout occurs really quickly. That's probably why this test is the most effective one at reproducing the issue :). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
