[BanyanDB] Parameterize max opened blocks

[hanahmily]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

BanyanDB server implements a priority queue to :

• Control the number of opened blocks. This strategy protects the server from massive querying.
• Close inactive blocks after a period.

The group’s physical options should add these options:

• max_active_blocks_num indicates the max number of opened blocks. If a query will touch blocks more than this setting, an error should be returned. The default is 0 which means all blocks should be active.
• idle_timeout_seconds Max time in seconds that a block can remain idle in a shard. After this time, the shard will close this block. The default should be 0s, that means the shard never close a block.
• max_wait_seconds Amout of time a caller will wait until getting a block. The default is 60s.

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[hanahmily]

Since we will introduce a new unified memory layer, the opened blocks won't determine the memory usage of a shard.