Madelyn Olson

> We should probably add additional monitoring on the cluster bus connection sent buffer monitoring. E.g. if the buffer size is too large, close the connection. Something like the COB...

> I think that maintaining a buffer list per channel would help reduce the memory overhead of large clusters (when sharding is not used) somewhat similar to what was done...

Ok, in either case, @hpatro mentioned he wanted to pick this up. Assigning it myself to indicate it's being worked on.

> We'd have to scan through the listpack to check if all elements are integers. For integers, I think it seems more strait-forward to start off with an intset and...

Makes sense to me.

@yossigo Here is a dump of all of my thoughts. Once something seems like a good idea, we can split it off into its own issue and pursue it.

@zuiderkwast ideally no, the cluster actually has a blacklist today. The problem is that for large clusters it can be difficult to orchestrate them all agreeing that a node should...

> I don't know the history of the cluster very well. Why does the cluster not support the multi-dbs mode, are there any difficulties in technical implementation? Has it been...

> in my scenarios, a cluster would be shared in multiple callers, and using multiple db could reduce the dict overhead, I'd like to try it. Do you want to...

That is a pretty delightfully useless error message. We almost always see these errors when some external actor is trying to send messages to the clusterbus. All cluster bus messages...