kafka

Is your feature request related to a problem?

The first step towards app optimization

Please describe.
Configure whyDidYouRender under the development env

**Note: make sure it is compatible with all the custom hooks that we are using in the project **

Similar to LATSET_BY_OFFSET and COLLECT_LIST users may want to have a "bounded" COLLECT_LIST function that only collects the latest N elements instead of the (default) behavior of collecting the first N elements.

For an implementation of #126 (PostgreSQL driver with SKIP LOCKED), I create a SQL table for each consumer group containing the offsets ready to be consumed. The name for these tables is build by concatenating some prefix, the name of the topic and the name of the consumer group. In some of the test cases in the test suite, UUID are used for both, the topic and the consumer group. Each UUID has

Today, unless developer_mode is true, we throw if there is less than 1G of free memory on startup.

Similar to how we recommend XFS, we can recommend that 1G memory be available, but allow things to work if less is available. Redpanda works for low memory situations, and not throwing allows us to drop into memory constrained environments more easily.