enable management of environments with non-default configurations about rkv HOT 1 OPEN

Ah, I see what you mean.

Looks like Manager is missing a "delete (close)" method in the following cases:

• Be able to close the env on-demand if the consumer has finished the interaction with rkv, and won't need it thereafter. Closing a rkv env will free up certain resources, such as reader/writer slots in the lockfile, opened db handles etc
• If a customer wants to open the rkv env with a different configurations, an env close is required as all the mdb_env_set functions (max_readers/max_dbs/max_map_size) need to be called after mdb_env_create and before mdb_env_open

So if a reconfiguration is needed, the customer has to "delete" the env in the Manager at the appropriate point, and then re-open it with the new setup.

from rkv.