Currently the environment variable ydb_poollimit is honored by MUPIP REORG and not by others (e.g. MUMPS, DSE, LKE, MUPIP BACKUP, MUPIP INTEG etc.). For MUMPS, the VIEW "POOLLIMIT" command is an alternate way to control the poollimit setting. But for all others (DSE, LKE, MUPIP BACKUP, MUPIP INTEG etc.) there is no way to control the poollimit setting. It would be desirable (and consistent) to have ydb_poollimit be honored by all executables in YottaDB (including MUMPS), not just MUPIP REORG.
Draft Release Note
MUMPS, DSE, LKE, MUPIP BACKUP etc. now honor the ydb_poollimit environment variable and sets the poollimit value at process startup. Previously only MUPIP REORG honored this env var. As for MUMPS, VIEW "POOLLIMIT" continues to be honored and overrides the poollimit setting initially set from the env var.
Final Release Note
Description
Currently the environment variable ydb_poollimit is honored by MUPIP REORG and not by others (e.g. MUMPS, DSE, LKE, MUPIP BACKUP, MUPIP INTEG etc.). For MUMPS, the VIEW "POOLLIMIT" command is an alternate way to control the poollimit setting. But for all others (DSE, LKE, MUPIP BACKUP, MUPIP INTEG etc.) there is no way to control the poollimit setting. It would be desirable (and consistent) to have ydb_poollimit be honored by all executables in YottaDB (including MUMPS), not just MUPIP REORG.
Draft Release Note
MUMPS, DSE, LKE, MUPIP BACKUP etc. now honor the ydb_poollimit environment variable and sets the poollimit value at process startup. Previously only MUPIP REORG honored this env var. As for MUMPS, VIEW "POOLLIMIT" continues to be honored and overrides the poollimit setting initially set from the env var.