Avi Kivity

Dequeued: ``` 18:40:13 + /jenkins/workspace/scylla-master/next/scylla/tools/toolchain/dbuild -v /var/cache/ccache:/var/cache/ccache:z -e CCACHE_DIR=/var/cache/ccache -e CCACHE_UMASK=002 -e PATH=/usr/lib64/ccache:/usr/bin:/usr/sbin -- ninja -j 48 18:40:13 + tee --append output-build-x86_64.txt 18:40:13 ninja: error: 'build/node_exporter', needed by 'build/debug/dist/tar/scylla-unstripped-x86_64-package.tar.gz', missing...

@yaronkaikov @benipeled is release engineering prepared for it? We'll need to keep both copies of the package. Also, @bhalevy this will break backtrace.scylladb.com so it needs to be adjusted.

> @avikivity ping Why me?

Ah, it was open so I thought not fixed. But I see there are fixes merged.

/cc @bhalevy

The exception mentions being able to allocate 16MB of memory. How does having 128k or 256k make any difference?

The problem is not the changelog. The problem is that I don't understand how the patch fixes the problem. It shouldn't matter if there are 128k free, 256k free, default_fragment_size...

Nice, looks good.

Note, truncate is not a critical operation. The usual way it is used is that the workload is acquiesced and then a truncate is issued.

It doesn't need CL=ALL, just QUORUM. If a replica misses the truncate tombstone then reconciliation will apply it there retroactively.