hindsight-admin export-bank is OOM-killed on a 57k-unit bank inside a 5 GB container
Setup: self-hosted Hindsight 0.10.0 (ghcr.io/vectorize-io/hindsight full image), container mem_limit: 5g, bank with 3,786 documents / 57,499 memory units / 2.3 M links.
Observed: hindsight-admin export-bank --bank JervCoding --output /tmp/x.zip prints "Exporting bank 'JervCoding' from schema 'public'..." and is OOM-killed (exit 137; dmesg: Memory cgroup out of memory: Killed process … (hindsight-admin) anon-rss:4750944kB), three attempts. hindsight-admin backup of the whole database (23 tables, 4.8 M rows) succeeds in the same container, so the export path appears to materialise the bank in memory rather than streaming it. POST /v1/default/banks/{id}/transfer/export returns 404 on 0.10.0 (docs describe it), and rename-bank is not in the 0.10.0 admin CLI.
Ask: stream export-bank (it is the documented blue-green migration path), or document its memory requirement per bank size.
Source: vectorize-io/hindsight