[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesos-issues
Subject:    [jira] [Created] (MESOS-10232) Old sandboxes not being GC'ed caused frequent Mesos GC
From:       "HAO SU (Jira)" <jira () apache ! org>
Date:       2021-10-01 4:48:00
Message-ID: JIRA.13404402.1633063667000.1088808.1633063680239 () Atlassian ! JIRA
[Download RAW message or body]

HAO SU created MESOS-10232:
------------------------------

             Summary: Old sandboxes not being GC'ed caused frequent Mesos G=
C
                 Key: MESOS-10232
                 URL: https://issues.apache.org/jira/browse/MESOS-10232
             Project: Mesos
          Issue Type: Bug
          Components: agent
            Reporter: HAO SU


Customers reported that their logs (sandbox files) are missing soon after t=
he job completes.=C2=A0Mesos agent logs indicate that the files were GC-ed =
within minutes of container exit. Checking the host, there were a lot of ol=
d sandboxes dating back to Jan 2020. These are occupying a lot of space (~8=
8% of all sandbox usage) and likely causing frequent GC of recently running=
 containers.=C2=A0

Mesos does recognize these sandbox and try to schedule them for deletion
{code:java}
 I0902 18:02:27.511576 467334 gc.cpp:95] Scheduling '/var/lib/mesos/meta/sl=
aves/68caec4c-6ea5-44e7-9f8-fad1922d5-S162/frameworks/3dcc744f-016c-6579-9b=
82-6325402d2-9999/executors/fa00-29a3-4c47-95fd-808d52ac53-13-1' for gc -85=
.5641509780737weeks in the future
{code}
but the deletion seems to never happen.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[prev in list] [next in list] [prev in thread] [next in thread]