Hello everyone, Can somebody tell me why the `data...
# troubleshoot
f
Hello everyone, Can somebody tell me why the
datahub-actions
container uses so much space? I am using the quickstart image and it rapidly increased to 15gb when I tried to ingest the tables I have on redshift… And I am not even using actions 😆 Any help would be appreciated 🫶
a
Hi, what version are you using- this seems like it could be a bug
f
Hi Paul! more info from today: I was trying to run a (big) ingestion and I ran into a
no space left on device
error. Note that this is running using the docker-compose quickstart on an ec2 with an attached volume of 50gb 😅 I did some checks and it seems to be related indeed with actions:
docker system df
results in:
Copy code
TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          18        12        13.21GB   3.048GB (23%)
Containers      12        7         25.43GB   23.3kB (0%)
Local Volumes   14        9         11.72GB   134.2MB (1%)
Build Cache     0         0         0B        0B
if I look at the containers, the main problem is with:
Copy code
acryldata/datahub-actions:head              "/bin/sh -c 'dockeri…"    0               22.2GB    5 days ago   Up 5 days                  datahub-datahub-actions-1
Also theres an unamed heavy volume of 10gb, if I inspect it, the folder structure looks as follows:
Copy code
cleaner-offset-checkpoint  __consumer_offsets-18  __consumer_offsets-28  __consumer_offsets-38	__consumer_offsets-48	     MetadataChangeEvent_v4-0
__consumer_offsets-0	   __consumer_offsets-19  __consumer_offsets-29  __consumer_offsets-39	__consumer_offsets-49	     MetadataChangeLog_Timeseries_v1-0
__consumer_offsets-1	   __consumer_offsets-2   __consumer_offsets-3	 __consumer_offsets-4	__consumer_offsets-5	     MetadataChangeLog_Versioned_v1-0
__consumer_offsets-10	   __consumer_offsets-20  __consumer_offsets-30  __consumer_offsets-40	__consumer_offsets-6	     MetadataChangeProposal_v1-0
__consumer_offsets-11	   __consumer_offsets-21  __consumer_offsets-31  __consumer_offsets-41	__consumer_offsets-7	     meta.properties
__consumer_offsets-12	   __consumer_offsets-22  __consumer_offsets-32  __consumer_offsets-42	__consumer_offsets-8	     PlatformEvent_v1-0
__consumer_offsets-13	   __consumer_offsets-23  __consumer_offsets-33  __consumer_offsets-43	__consumer_offsets-9	     recovery-point-offset-checkpoint
__consumer_offsets-14	   __consumer_offsets-24  __consumer_offsets-34  __consumer_offsets-44	DataHubUpgradeHistory_v1-0   replication-offset-checkpoint
__consumer_offsets-15	   __consumer_offsets-25  __consumer_offsets-35  __consumer_offsets-45	DataHubUsageEvent_v1-0	     replication-offset-checkpoint.tmp
__consumer_offsets-16	   __consumer_offsets-26  __consumer_offsets-36  __consumer_offsets-46	log-start-offset-checkpoint  _schemas-0
__consumer_offsets-17	   __consumer_offsets-27  __consumer_offsets-37  __consumer_offsets-47	MetadataAuditEvent_v4-0
I don’t know if this is related but I thought it was a bunch of space
a
Yeah wow! Any chance you could log a git bug here? Do you have actions set up acting on stuff? It seems like a bug that actions would hog that much space
CC: @echoing-airport-49548