Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients

Problem description

I saw comment about nulls caching dotnetcore/EasyCaching#43 (comment), but we have important case when it is necessary.

We develop a low code platform, where our clients can set up some handlers for processing some requests from there websites.

1. Each handler is entity in database, that is cached in memory.
2. Some handlers cou

使用kubectl edit或者kubctl replace修改alluxioruntimes的yaml后，controller不会watch此事件并重新创建pod。
建议新增动态修改的机制。