graphql-engine icon indicating copy to clipboard operation
graphql-engine copied to clipboard

Out of memory when click reload enum or reload metadata

Open phamquyhai opened this issue 3 years ago • 1 comments

Version Information

Server Version: v2.10.0-beta.1 CLI Version (for CLI related issue): v2.9.0

How to reproduce the issue?

  • Click reload enum in table settings
  • Click Reload metadata in console/settings/metadata-actions

Screenshots or Screencast

2022-07-31T04:24:43.605 app[b2fcf266] sin [info] [ 39.468174] Out of memory: Killed process 520 (graphql-engine) total-vm:1074267988kB, anon-rss:202192kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:524kB oom_score_adj:0

2022-07-31T04:24:44.268 app[b2fcf266] sin [info] Main child exited normally with code: 137

2022-07-31T04:24:44.268 app[b2fcf266] sin [info] Starting clean up.

2022-07-31T04:24:51.437 runner[b2fcf266] sin [info] Starting instance

2022-07-31T04:24:51.556 runner[b2fcf266] sin [info] Configuring virtual machine

2022-07-31T04:24:51.557 runner[b2fcf266] sin [info] Pulling container image

2022-07-31T04:24:53.746 runner[b2fcf266] sin [info] Unpacking image

2022-07-31T04:24:53.750 runner[b2fcf266] sin [info] Preparing kernel init

2022-07-31T04:24:53.997 runner[b2fcf266] sin [info] Configuring firecracker

2022-07-31T04:24:54.245 runner[b2fcf266] sin [info] Starting virtual machine

phamquyhai avatar Jul 31 '22 04:07 phamquyhai

This issue may be a lack of computing resources in your infrastructure.

We do know that metadata reload is expensive, memory wise.

Can you confirm whether you face this issue on older versions of hasura, on the same infra?

BenoitRanque avatar Aug 08 '22 15:08 BenoitRanque

Closing with answer from @BenoitRanque. Please reopen if it's an actual bug. Thanks.

seanparkross avatar Aug 25 '22 11:08 seanparkross