Re: [PROPOSAL] Change the default value of conserve-sockets to false

2020-12-03 Thread Anilkumar Gingade
I was conversing with few of the dev's about requirement of different settings/configuration for set of nodes in the cluster depending on the business/application needs; for example set of nodes serving different kind of application requirement (data store) than other nodes in the cluster (comp

Re: [PROPOSAL] Change the default value of conserve-sockets to false

2020-12-03 Thread Bruce Schuchardt
+1 for having the default be conserve-sockets=false. Any time there has been trouble and conserve-sockets=true is involved we always suggest changing it to false. On 12/3/20, 6:58 AM, "Anilkumar Gingade" wrote: I was conversing with few of the dev's about requirement of different sett

Re: [PROPOSAL] Change the default value of conserve-sockets to false

2020-12-03 Thread Barrett Oglesby
Anil, you wrote: - We need to be thinking about auto setting of configuration values (dynamic) based on the load, resource availability and service agreements. It would be cool to eventually remove this property altogether and auto-configure it. Besides the things you mention, another thing tha

[PROPOSAL] backporting GEODE-8764 to 1.13 and 9.10

2020-12-03 Thread Xiaojian Zhou
GEODE-8764 is an enhanced version of GEODE-6930. Lucene functions should only require DATA:READ permission on the specified region, no need to gain permission on other unrelated regions. The fix has no risk. Regards Xiaojian Zhou